kubernetes scheduling ai_generated true

0/3 nodes are available: 3 Insufficient cpu

ID: kubernetes/pod-unschedulable

Also available as: JSON · Markdown
91%Fix Rate
93%Confidence
50Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
8 active — — —

Root Cause

No node has enough CPU or memory to schedule the pod.

generic

Workarounds

  1. 93% success Review and right-size resource requests: kubectl top nodes to see actual usage 
    Requests may be over-provisioned; reduce to actual needs

    Sources: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/

  2. 90% success Add more nodes or use cluster autoscaler to scale up automatically 
    autoscaler provisions new nodes when pods can't be scheduled

Dead Ends

Common approaches that don't work:

  1. Removing resource requests to bypass scheduling 75% fail

    Pod can be scheduled anywhere but may OOM or starve other pods

  2. Draining a node to free resources 60% fail

    Moves pods to other nodes; doesn't add capacity

Error Chain

Frequently confused with: