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).