Court-records operators find kube-scheduler is not scheduling after a network partition, and leader-election leases look stuck. What concept explains this failure mode?
Select an answer to reveal the explanation.
Short Explanation
HA control-plane pieces elect a captain. After a partition, if nobody can hold the lease cleanly, the scheduler sits idle—even though pods are waiting—until leadership is clear again.
Full Explanation
Components such as kube-scheduler participate in leader election so only one instance actively schedules. Network partitions can disrupt lease renewals and delay or split leadership, leaving the cluster without an active scheduler. Claiming schedulers never elect a leader, that only CoreDNS elects leaders, or that partitions auto-bind pods is incorrect.