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
{{ message }}
Repository navigation
Commit 0083245
Browse filesBrowse the repository at this point in the historyBrowse files
authored
fix: trigger failover when the primary node becomes unreachable (#10448)
When the node hosting the primary loses network connectivity, the
kubelet can no longer update the pod status. The pod's ContainersReady
condition is left stale as True, while Kubernetes actively sets Ready to
False via the node controller. By checking Ready instead of
ContainersReady, the operator can now correctly detect that the primary
is unavailable and proceed with a failover.
This change is safe in combination with the previous patch: when the
status endpoint fails transiently the pod's Ready condition is still
True, so the operator requeues rather than triggering a spurious
failover.
See #10403
Signed-off-by: Leonardo Cecchi <[email protected]>
Signed-off-by: Armando Ruocco <[email protected]>
Signed-off-by: Marco Nenciarini <[email protected]>
Co-authored-by: Marco Nenciarini <[email protected]>
Co-authored-by: Armando Ruocco <[email protected]>
0 commit comments