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
only report Progressing for active network rollouts
Keep pod-based Progressing tied to an actual CNO rollout instead of
temporary unavailability during node reboot churn. Persist the rollout
generation in status manager state so Progressing stays true until the
rollout is both observed and fully available.
For machine config status, stop treating generic MCP node convergence as
a CNO rollout signal. Check whether the CNO machine config is still
present in the pool's rendered source list so routine MCO updates do not
flip network Progressing to true.
Also persist install completion in the same annotation so a restarted CNO
does not fall back into startup-only Progressing paths during a cluster
upgrade. That prevents noncritical networking pods from briefly setting
Progressing=true after the actual network rollout is already complete.
Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
Co-Authored-by: Claude Code and Codex
0 commit comments