Question

A developer deploys a Pod that requests 4Gi of memory and 2 CPU cores. After applying the manifest, the Pod remains in the Pending state. The cluster has three worker nodes, each with 3Gi of allocatable memory and 4 allocatable CPU cores. What is the most likely reason the Pod cannot be scheduled?

Accepted Answer

No node has enough allocatable memory to satisfy the Pod's memory request of 4Gi.

Answer

The Pod's CPU request of 2 cores exceeds the total CPU available across the cluster.

Answer

The kube-scheduler is not running, so no Pods can be scheduled to any node.

Answer

The Pod is missing a nodeSelector, which is required for the scheduler to place it.