Repository navigation
feat(operator): a quorum member whose node is gone gets a new volume on another node - #672
Merged
Merged
Conversation
…on another node O6 of plans/operator-kates-kind.md. Members are pod names, reached through a Service each, so a replacement needs no membership change: the same member comes back on an empty disk and catches up from the leader. - A member pod Pending because its volume can only be on another node, for two minutes, has its claim and its pod deleted; the StatefulSet makes both again. One at a time, and only while every other member follows a leader and has caught up. With no leader nothing is replaced; Ready=False reason MemberLost says why. - A pending pod whose claim is gone or going is deleted, so it does not wait on the old claim. - Members prefer one node each (preferred pod anti-affinity on hostname), so a lost node takes one member, not the majority. - The chart lets the operator get and delete PersistentVolumeClaims in the namespaces it watches, in both RBAC scopes. - operator/e2e-node-loss.sh deletes a Kind worker node holding a follower and its volume. Not in CI, whose Kind has one node.
This was referenced Nov 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
O6 of
plans/operator-kates-kind.md: replace a member whose node is gone.Why no membership API
Members are identified by pod name, and each is reached through a Service of its own, so a member that comes back on a new disk has the same id and the same address. Ratis brings it up to date from the leader. Scaling (O5) is the only thing that needs membership changes, and it is not part of this PR.
What changes
Pendingfor 2 minutes, because its volume can only be on another node, has its claim and its pod deleted. TheStatefulSetthen makes both again on a node that exists.Ready=Falsewith reasonMemberLostsays why.kubernetes.io/hostname). This only places new volumes: members that already share a node with node-local storage stay there until their volume is replaced.getanddeletepersistentvolumeclaims, in both RBAC scopes.The lost member is detected from the scheduler's message, in both its old and new wording (marked
shortcut:). The operator has no rights to read Nodes or PersistentVolumes, and this PR doesn't add any.Proof
lost(): replaced only under a settled leader; two lost of five handled one at a time; waits while another member catches up; no leader means nothing is done.operator/e2e-node-loss.shon a Kind cluster with three nodes: a worker node holding a follower and its volume was stopped and deleted. The member ran on another node with a new volume 184 s later, the leader never changed, the quorum was Ready with three members, and the new member caught up (applied index 162).the quorum has no leader to replace it under.