medium10 pts · first answer countskubernetesresource-management

Pod stuck Pending on CPU

A Pod stays Pending with this event, although node dashboards show CPU usage around 20 percent. What explains it?

Warning  FailedScheduling  default-scheduler
  0/5 nodes are available: 5 Insufficient cpu.
  preemption: 0/5 nodes are available: 5 No preemption victims found.

A.The nodes are low on disk space, which the scheduler reports as Insufficient cpu.B.The container image is too large to fit in the image cache of any of the five nodes.C.The Pod must define a liveness probe before the scheduler is allowed to place it.D.Scheduling uses summed CPU requests, not real usage, and requests already fill each node.

← ImagePullBackOff from a private registry Exit code 137 →