A canary rollout has progressed through 3 of 5 steps. A critical bug is found in the canary version. An engineer runs `kubectl argo rollouts abort my-rollout`. What is the resulting state of the Rollout?

Question

Accepted Answer

C. The canary ReplicaSet is scaled down to zero, all traffic returns to the stable ReplicaSet, and the Rollout phase becomes Aborted (displayed as Degraded). Aborting an Argo Rollout causes the controller to immediately scale the canary ReplicaSet to zero replicas and route all traffic back to the stable ReplicaSet. The Rollout enters the `Aborted` phase. To fix the issue and redeploy, the operator must update the pod template in the Rollout spec to trigger a new rollout revision.

A canary rollout has progressed through 3 of 5 steps. A critical bug is found in the canary version. An engineer runs `kubectl argo rollouts abort my-rollout`. What is the resulting state of the Rollout?

Related Questions

Discussion

A canary rollout has progressed through 3 of 5 steps. A critical bug is found in the canary version. An engineer runs kubectl argo rollouts abort my-rollout. What is the resulting state of the Rollout?

Related Questions

Discussion

A canary rollout has progressed through 3 of 5 steps. A critical bug is found in the canary version. An engineer runs `kubectl argo rollouts abort my-rollout`. What is the resulting state of the Rollout?