Pending Pods on a Cluster With Free Capacity
The report, in their words
Scaling a Deployment from 6 to 10 replicas has left four pods Pending for twenty minutes. The cluster dashboard reads 38% CPU and 41% memory used across fourteen nodes, so there is obviously room. Two more nodes were added an hour ago and the pods are still Pending.
Pull evidence
One item at a time, and nothing here tells you which one matters. Deciding what is worth looking at is most of the diagnosis.
kubectl describe pod — the scheduler event
The pod's resource requests
kubectl describe node — a typical worker
Cluster-wide free capacity
What the running replicas actually use
The two nodes added this morning
Node taints
Affinity and topology spread constraints
Namespace ResourceQuota
0 of 9 inspected. You are not required to open all of them — a real investigation is judged on how few you needed.
What is your diagnosis?
Commit to one. Nothing below is shown until you do.
Guessing wrong and being told exactly why is the point of this page. Reading the answer first is not practice.