Municipal workloads stay Pending with events citing insufficient CPU on every node, yet all nodes are Ready. What distinguishes this from a node-health outage?
Select an answer to reveal the explanation.
Short Explanation
Ready nodes with Pending pods is often a packing problem, not a corpse problem—everyone’s alive, there’s just no free CPU seats left.
Full Explanation
Scheduler Pending events for insufficient CPU indicate that no node has enough allocatable CPU for the pod’s requests, even when nodes report Ready. That is capacity exhaustion, not necessarily kubelet downtime, API certificate failure, or CoreDNS ConfigMap emptiness.