medium10 pts · first answer countskubernetestroubleshooting

Pod stuck Pending: Insufficient cpu

A new pod stays in Pending and kubectl describe shows the event below. What is the cause?

Warning  FailedScheduling  default-scheduler
0/3 nodes are available: 3 Insufficient cpu.

A.The container image cannot be pulled from the private registryB.The liveness probe keeps failing and kills the containerC.CPU requests exceed free allocatable CPU on all nodesD.The Service selector does not match the pod labels

← Logs from a crashed container Container exit code 137 OOMKilled →