Pod stuck in Pending state in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is a Kubernetes Pod stuck in Pending state?

A Pod in Kubernetes is stuck in the Pending state. What is the most common reason for this?

A There are not enough resources available on any node to schedule the Pod.

B The Pod's container image is missing from the registry.

C The Pod's network policy is blocking all traffic.

D The Pod has completed its task and is terminating.

💡 Hint

Think about what the scheduler needs to place a Pod on a node.

A Pod stays in Pending state if Kubernetes cannot find a node with enough CPU, memory, or other requested resources to run it.

💻 Command Output

intermediate

Identify the cause from Pod describe output

Given the following snippet from kubectl describe pod mypod, what is the cause of the Pod being Pending?

Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  2m (x3 over 5m)    default-scheduler  0/3 nodes are available: 3 Insufficient memory.

A The Pod's container image is not found.

B The Pod is waiting for a volume to be attached.

C The Pod requests more memory than any node has available.

D The Pod's service account is missing.

💡 Hint

Look at the 'FailedScheduling' message carefully.

The scheduler reports 'Insufficient memory' meaning no node has enough free memory to run the Pod.

❓ Troubleshoot

advanced

Fixing a Pod stuck in Pending due to node selector mismatch

You deployed a Pod with a nodeSelector that does not match any node labels. Which command will help you verify node labels to fix this issue?

A kubectl logs mypod

B kubectl describe pod mypod

C kubectl get pods --all-namespaces

D kubectl get nodes --show-labels

💡 Hint

You need to check node labels to match the nodeSelector.

The command kubectl get nodes --show-labels lists all nodes with their labels, helping you verify if the nodeSelector matches any node.

🔀 Workflow

advanced

Order the steps to diagnose a Pending Pod due to resource constraints

Put the following steps in the correct order to diagnose why a Pod is stuck in Pending due to resource constraints.

A 1,3,2,4

B 3,1,2,4

C 1,3,4,2

D 3,2,1,4

💡 Hint

Start by checking Pod events, then resource requests, then node details, then compare.

First, check Pod events to see scheduling errors. Then verify Pod resource requests. Next, check node resources. Finally, compare requests to availability to find the mismatch.

✅ Best Practice

expert

Preventing Pods from getting stuck in Pending state

Which practice helps prevent Pods from getting stuck in Pending state due to resource shortages?

A Use hostPath volumes to store Pod data on the node.

B Always set resource requests and limits for Pods to help the scheduler make decisions.

C Disable the Kubernetes scheduler and assign Pods manually.

D Set Pod restartPolicy to Never.

💡 Hint

Think about how the scheduler decides where to place Pods.

Setting resource requests and limits allows the scheduler to allocate Pods only to nodes with enough resources, preventing Pending state due to resource shortages.