New county workloads stay Pending with no nodeName and events do not show ordinary capacity or affinity fit failures. Which control-plane component failure best explains this?
Select an answer to reveal the explanation.
Short Explanation
Pending with no node name is the scheduler's empty desk—nobody is assigning seats. If capacity and affinity look fine, check that kube-scheduler itself is alive and holding leadership.
Full Explanation
The scheduler binds pods to nodes. When it is down or stuck without a leader, new pods remain Pending without a nodeName and without the usual FailedScheduling capacity messages. kube-proxy affects Service dataplane after pods run; CoreDNS is not required for binding; CSI issues affect volume provisioning, not every unschedulable pod without volumes.