Investigate a Pod that remains Pending.

Instruction: Use the manifest and node evidence to explain placement, propose a justified correction and define a verification check.

Context:

A fictional batch Pod remains Pending while CPU dashboards look quiet. This is the complete resource request for its only container; it has no init containers or Pod overhead. The listed nodes are all eligible, with no additional affinity, taint or volume constraint. Values are from the same snapshot.

apiVersion: v1
kind: Pod
metadata:
  name: invoice-worker
spec:
  restartPolicy: Never
  containers:
    - name: worker
      image: registry.example/invoice-worker:v1
      resources:
        requests:
          cpu: "3"
          memory: "512Mi"
        limits:
          cpu: "3"
          memory: "512Mi"
NodeAllocatable CPUExisting CPU requestsObserved CPUAvailable memory
node-a2 cores0.4 cores20%4 GiB
node-b2 cores0.6 cores20%4 GiB

The scheduling event reports insufficient CPU. Explain whether adding a third node with the same capacity would help.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

The Pod requests three cores, but neither eligible node has even three allocatable cores before existing requests are counted...

Upgrade to view official answer

Related Questions