Pod stuck in Pending state in Kubernetes - Step-by-Step Execution

Process Flow - Pod stuck in Pending state

Pod Created

↓

Scheduler Checks Resources

↓

Resources Available?

No→Pod Stays Pending

Yes↓

Pod Scheduled to Node

↓

Pod Starts Running

This flow shows how a pod moves from creation to running, or stays pending if resources are insufficient.

Execution Sample

Kubernetes

kubectl get pods
kubectl describe pod mypod
kubectl get nodes
kubectl describe node nodename

Commands to check pod status, details, and node resources to diagnose Pending state.

Process Table

Step	Action	Condition/Check	Result	Next Step
1	Pod created by user	N/A	Pod enters Pending state	Scheduler checks resources
2	Scheduler checks nodes for resources	Are nodes free with enough CPU/memory?	No nodes available	Pod remains Pending
3	User runs 'kubectl describe pod mypod'	Check events for reasons	Shows 'Insufficient cpu' event	User checks nodes
4	User runs 'kubectl get nodes'	Check node status and capacity	Nodes Ready but CPU fully used	User considers scaling or freeing resources
5	User runs 'kubectl describe node nodename'	Check detailed resource usage	Confirms no free CPU	Pod stays Pending until resources free
6	User frees resources or adds nodes	Resources become available	Scheduler assigns pod to node	Pod moves to Running state
7	Pod starts running	Pod status changes	Pod Ready	End

💡 Pod stays Pending if no nodes have enough free resources; moves to Running once scheduled.

Status Tracker

Variable	Start	After Step 2	After Step 4	After Step 6	Final
Pod Status	Pending	Pending	Pending	Running	Running
Node CPU Availability	Unknown	Insufficient	Insufficient	Sufficient	Sufficient

Key Moments - 3 Insights

Why does the pod stay in Pending even though nodes are Ready?

Nodes can be Ready but still have no free CPU or memory. Execution table step 4 shows nodes are Ready but CPU is fully used, so pod cannot be scheduled.

What does the 'Insufficient cpu' event mean in pod description?

It means the scheduler tried to find a node with enough CPU but failed. See execution table step 3 where this event is found, indicating resource shortage.

How can the pod move from Pending to Running?

By freeing resources or adding nodes to increase available CPU/memory. Step 6 shows that once resources are sufficient, scheduler assigns the pod and it starts running.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the pod status change from Pending to Running?

A Step 2

B Step 6

C Step 4

D Step 3

💡 Hint

Check the 'Pod Status' variable in variable_tracker after Step 6.

According to the execution table, what is the main reason the pod stays Pending at Step 2?

A No nodes have enough CPU resources

B Node is Not Ready

C Pod configuration error

D Network issue

💡 Hint

See Step 2 'Result' column and variable_tracker 'Node CPU Availability' after Step 2.

If the user adds more nodes with free CPU, how will the pod status change in the variable_tracker?

A Pod Status remains Pending

B Node CPU Availability becomes Insufficient

C Pod Status changes to Running

D Pod Status changes to Failed

💡 Hint

Refer to Step 6 and final values in variable_tracker.

Concept Snapshot

Pod Pending State:
- Pod created but not scheduled yet
- Scheduler checks node resources
- Pending if no node has enough CPU/memory
- Check 'kubectl describe pod' for events
- Free resources or add nodes to schedule pod
- Pod moves to Running once assigned

Full Transcript

When you create a pod in Kubernetes, it starts in Pending state until the scheduler finds a node with enough resources. The scheduler checks all nodes for available CPU and memory. If no node has enough free resources, the pod stays Pending. You can use 'kubectl describe pod' to see events like 'Insufficient cpu' that explain why scheduling failed. Checking nodes with 'kubectl get nodes' and 'kubectl describe node' helps confirm resource availability. To fix Pending pods, free resources or add nodes. Once resources are sufficient, the scheduler assigns the pod to a node and it starts running.