Revert "UPSTREAM: <carry>: Bump github.com/argoproj/argo-workflows/v3…

[hbelmiro]

… from v3.3.10 to v3.5.8"

This reverts commit 38ce527.

cc @DharmitD @gregsheremeta @gmfrasca

[gmfrasca]

/lgtm

[DharmitD]

/lgtm
/Approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DharmitD

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [DharmitD]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dsp-developers]

Commit Checker results:

**NOTE**: These are the results of the commit checker scans. 
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between ed99781d11e74ecc6541142e559aabb877f9c8d2...eb9b96cf5d76f553c7f42f0fee3e32534082633f

[dsp-developers]

Commit Checker results:

**NOTE**: These are the results of the commit checker scans. 
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 0 commits between ed99781d11e74ecc6541142e559aabb877f9c8d2...eb9b96cf5d76f553c7f42f0fee3e32534082633f

[dsp-developers]

A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-60
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-60
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-60
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-60
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-60
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-60

[dsp-developers]

An OCP cluster where you are logged in as cluster admin is required.

The Data Science Pipelines team recommends testing this using the Data Science Pipelines Operator. Check here for more information on using the DSPO.

To use and deploy a DSP stack with these images (assuming the DSPO is deployed), first save the following YAML to a file named dspa.pr-60.yaml:

apiVersion: datasciencepipelinesapplications.opendatahub.io/v1alpha1
kind: DataSciencePipelinesApplication
metadata:
  name: pr-60
spec:
  dspVersion: v2
  apiServer:
    image: "quay.io/opendatahub/ds-pipelines-api-server:pr-60"
    argoDriverImage: "quay.io/opendatahub/ds-pipelines-driver:pr-60"
    argoLauncherImage: "quay.io/opendatahub/ds-pipelines-launcher:pr-60"
  persistenceAgent:
    image: "quay.io/opendatahub/ds-pipelines-persistenceagent:pr-60"
  scheduledWorkflow:
    image: "quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-60"
  mlmd:  
    deploy: true  # Optional component
    grpc:
      image: "quay.io/opendatahub/mlmd-grpc-server:latest"
    envoy:
      image: "registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2"
  mlpipelineUI:
    deploy: true  # Optional component 
    image: "quay.io/opendatahub/ds-pipelines-frontend:pr-60"
  objectStorage:
    minio:
      deploy: true
      image: 'quay.io/opendatahub/minio:RELEASE.2019-08-14T20-37-41Z-license-compliance'

Then run the following:

cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines.git
cd data-science-pipelines/
git fetch origin pull/60/head
git checkout -b pullrequest eb9b96cf5d76f553c7f42f0fee3e32534082633f
oc apply -f dspa.pr-60.yaml

More instructions here on how to deploy and test a Data Science Pipelines Application.