You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v3 is not intended to introduce significant breaking changes for most users. Please read the "Known issues" and "Breaking changes" to determine if you might be impacted.
Known Issues
Some users are reporting that the UI attempts to open all listing workflows in all namespaces, even if the user does not have access. To work-around - append the correct namespace in the URL.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Quick Start
What's New?
Find out in our blog post
Migration From v2
v3 is not intended to introduce significant breaking changes for most users. Please read the "Known issues" and "Breaking changes" to determine if you might be impacted.
Known Issues
Breaking Changes
chore(server): Enable TLS by default. Resolves #5205 (#5212)
The server now starts with TLS enabled by default if a key is available. This can be disabled using
--secure=false
.If you have an ingress, you may need to add the appropriate annotations:(varies by ingress):
Argo CLI
Mac
Available via
curl
Linux
Available via
curl
Argo Controller
Since
v3.0.4
Since
v3.0.3
podSpecPatch
can result in failed workflowpodSpecPatch
can result in failed workflow #5897Contributors
This discussion was created from the release v3.0.5.
Beta Was this translation helpful? Give feedback.
All reactions