Canary Rollback #2059
Unanswered
dlennon-ie
asked this question in
Q&A
Canary Rollback
#2059
Replies: 1 comment
-
Hello The Rollout is set to degraded because the new release was not deployed The old version is still running and is perfectly healthy. There is nothing else to do. You are expected to fix the error and redeploy in order to get a "healthy" version. Not also that ArgoCD health status and Argo Rollouts status is not 1-1 mapping. It is manually mapped via the health check https://github.com/argoproj/argo-cd/blob/master/resource_customizations/argoproj.io/Rollout/health.lua |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
Trying to figure out how to abort a canary rollout and return the rollout to a healthy status.
Whenever I abort a canary rollout the traffic is moved off successfully however the Rollout status is set to degraded.
What is the correct approach to rollback a canary release?
Beta Was this translation helpful? Give feedback.
All reactions