chore(backend): bump argo-workflows to latest.

[jmcarp]

Description of your changes:

Try to upgrade argo-workflows based on previous PRs. Resolves #6916.

Checklist:

• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[google-oss-prow]

Hi @jmcarp. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[zijianjoy]

Can you also update https://github.com/kubeflow/pipelines/tree/master/manifests as well? Examples: a89183f#diff-75d17c1c8ea73190533f46fa0bfb393085b8f96b0587c51622e8f9388fd23477

[zijianjoy]

/ok-to-test

[zijianjoy]

You will need to update .cloudbuild.yaml and .release.cloudbuild.yaml as well: a89183f#diff-51ad04b116a62f170e26dd77721528424f95fbc1df7adcd2a325bdaa100dac08

I realized that this step will need to be done by me. I will do this step.

[zijianjoy]

@jmcarp Would you mind granting me edit permission to your branch? https://github.com/jmcarp/pipelines/tree/jmcarp/argo-workflows-v3.2 So I can push images based on your change.

[jmcarp]

Do you not have access to my fork? Maintainers should be allowed to push:

And I invited you to my fork:

[jmcarp]

@zijianjoy let me know if I need to do anything else you give you access to my branch.

[zijianjoy]

/retest-required

I have pushed the license compliance images.

[jmcarp]

/retest-required

[zijianjoy]

Question: Why do we need to upgrade golang version for presubmit in this PR?

[zijianjoy]

Creating PR to supplement your argo workflow change: jmcarp#1.

I was not able to directly push to your branch since the name has changed to jmcarp/argo-workflows-v3.2 (I guess having slash / in the branch name is a bit tricky to push commits to this remote branch, maybe it is conflicting with the repository name)

[zijianjoy]

/lgtm
/approve

Thank you for your PR!

[zijianjoy]

/assign @Bobgy

[jmcarp]

Hi @Bobgy, would it be possible to get this into the 1.8 release?

[Bobgy]

/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bobgy, zijianjoy

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 [Bobgy]

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