A new parks-api Pod stays Pending. kubectl describe shows FailedScheduling with Insufficient cpu, and the Pod’s requests.cpu is 4 on nodes that each have about 2 allocatable cores left. What is the most accurate diagnosis?
Select an answer to reveal the explanation.
Short Explanation
The scheduler is matching reservation sizes to free shelves. Ask for four cores when only two are free and the Pod sits Pending. That message is about requests at schedule time, not an OOM or image pull.
Full Explanation
The kube-scheduler filters nodes using resource requests, not limits. If no node has enough remaining allocatable CPU to satisfy the Pod’s CPU request, the Pod remains Pending with an Insufficient cpu scheduling event. Runtime conditions such as OOMKilled or ImagePullBackOff occur only after a Pod has been bound and started on a node.