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
A traffic routed rollout that is fully promoted (stableRS == currentPodHash), and then is aborted, will cause the controller to get into a hot loop where it continuously sets and unsets the scale-down-deadline on the desired ReplicaSet.
In one user's case, the controller would reconcile the same rollout up to 1000 times in a minute.
To Reproduce
Deploy this rollout and allow it to reach a healthy state:
jessesuen
changed the title
Aborting a fully-promoted rollout with traffic routing causes controller hot-loop
Aborting a fully-promoted traffic-routed rollout causes controller scale-down-deadline hot-loop
Aug 22, 2023
Describe the bug
A traffic routed rollout that is fully promoted (stableRS == currentPodHash), and then is aborted, will cause the controller to get into a hot loop where it continuously sets and unsets the
scale-down-deadline
on the desired ReplicaSet.In one user's case, the controller would reconcile the same rollout up to 1000 times in a minute.
To Reproduce
Expected behavior
Rollout should not get into a hot loop
Version
v1.4.1, v1.5.0
Logs
The text was updated successfully, but these errors were encountered: