How do "leader election" mechanisms work for Kubernetes controllers (such as kube-controller-manager or custom Operators) running with multiple replicas for high availability?
Correct! Well done.
Incorrect.
The correct answer is B) Multiple controller replicas run but use a distributed lock (a Lease object) to elect one active leader that performs reconciliation; if it fails or loses the lease, another replica takes over, giving high availability without conflicting actions
Correct Answer
Multiple controller replicas run but use a distributed lock (a Lease object) to elect one active leader that performs reconciliation; if it fails or loses the lease, another replica takes over, giving high availability without conflicting actions
Leader election via Lease objects ensures only one controller replica actively reconciles resources at a time (avoiding duplicate or conflicting actions), while standby replicas remain ready to take over quickly if the leader becomes unavailable.