-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature] Upgrade to latest Argo 3.4.x #10469
Comments
Previous upgrade attempt: #9301, in case anyone want to pick up and finish the work. |
/assign @Ayush9026 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
This was resolved in #10568 |
/area backend
What feature would you like to see?
Upgrade to latest Argo 3.4.x
What is the use case or pain point?
3.3 is no longer being patched with security fixes, and has not been for over a year now, lots of CVE's have accumulated since then, and KFP needs to catch up in this regard.
Is there a workaround currently?
A user can try to manually deploy Argo 3.4, but this has resulted in various issues:
WorkflowTaskResults
RBAC (argo 3.4 change) #8942POD_NAMES
change) #8935Related:
#9301
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered: