Update Argo manifest to 2.5.0

[rossella]

When using CRI-O, PNS executor fails with "executor error: Failed to determine pid for containerID xxxxxxxxxxxxx: container may have exited too quickly" .
This is due to argoproj/argo-workflows#2095
Updating argo fixes the issue.

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
kind/bug	0.62

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

[rossella]

We tested in our environment with argo workflow-controller 2.5.0 and argo-ui 2.4.2.
We had to apply the following changes:

• modify argo/base/custer-role.yaml adding for apiGroups argoproj.io the following resources: cronworkflows and workflowtemplates

Shall we go on and create a PR?

[Gsantomaggio]

I'd add that we ( I and @rossella ) were thinking to split the current Argo deploy in two sections:

• argo
• argo-ui

Since they are two different repositories.
We are already working on it, please let us know what you think about that, so we can prepare the PR.

Thank you

[Gsantomaggio]

@rossella I think we can close this issue. See kubeflow/pipelines#3537

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in one week if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been closed due to inactivity.

[Ark-kun]

/reopen
Kubeflow Pipelines does not work well with Argo < 2.4
Some people have issues since they install KFP from Kubeflow and get old Argo version.

[k8s-ci-robot]

@Ark-kun: Reopened this issue.

In response to this:

/reopen
Kubeflow Pipelines does not work well with Argo < 2.4
Some people have issues since they install KFP from Kubeflow and get old Argo version.

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.

[solarist]

Some people have issues since they install KFP from Kubeflow and get old Argo version.

We do too. We have installed a full on-prem installation of 1.1, and still see that the executor image is argoexec:v2.3.0, as well as the one set in the workflow-controller-configmap.

[yanniszark]

The work for upgrading Argo is tracked in the Kubeflow Pipelines repo.
kubeflow/pipelines#4553
kubeflow/pipelines#4693