when dynamicStableScale is enabled, the 2nd canary deployment (when the first one didn't finish) shifts the traffic to the stable 100% without waiting for it to scale up #3372
Labels
bug
Something isn't working
Checklist:
Describe the bug
When using canary strategy and adding
dynamicStableScale
if a newer release were pushed (v3) while an unstable release (v2) is still being deployed, argo rollouts controller will shift all the traffic to the stable release (v1) without waiting for it to scale up.To Reproduce
Just deploy a simple rollout with traffic routing and
dynamicStableScale
enabled, then change the image version to1.25.2
and apply the changes, now the v1 replicaset will have 1 replica while v2 will have 3, change the image to1.25.3
and the issue will happen, it will immediately shift all traffic to v1 without waiting for it pods to start, since we are using nginx as an example it will be very short, but on production, this caused an outageExpected behavior
It should act exactly like an abort on v2 so the traffic shifting to v1 will be gradual, and then move to v3
Version
1.6.0
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: