advancedHigh Availability: Multi-Node Control Plane & Leader Election
Why does only one Scheduler replica actually schedule Pods even when multiple replicas are running?
Multiple Scheduler/Controller Manager replicas use Kubernetes Lease-based leader election — only the replica currently holding the lease is active; the rest sit in standby and only take over if the current leader stops renewing its lease (crash, network partition).
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response