Bird
0
0

A Kubernetes pod is stuck in 'Pending' state after deployment. What is a common cause?

medium📝 Troubleshoot Q7 of 15
Docker - Production Patterns
A Kubernetes pod is stuck in 'Pending' state after deployment. What is a common cause?
AThe pod is running but not responding
BThe pod image is corrupted on the node
CNo available nodes meet the pod's resource requests
DThe pod has completed successfully
Step-by-Step Solution
Solution:

  1. Step 1: Understand 'Pending' pod state

    Pending means the pod is waiting to be scheduled, often due to resource constraints.

  2. Step 2: Evaluate options

    Corrupted image causes pull errors, completed pod is 'Succeeded', running but unresponsive is 'Running'.

  3. Final Answer:

    No available nodes meet the pod's resource requests -> Option C

  4. Quick Check:

    Pending pod = waiting for resources [OK]
Quick Trick: Pending pods usually wait for resources or scheduling [OK]
Common Mistakes:
  • Confusing Pending with Running or Failed
  • Assuming image corruption causes Pending
  • Thinking pod completed means Pending

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Docker Quizzes
Docker Security - Capabilities and privilege control - Quiz 2easy Docker Security - Scanning images for vulnerabilities - Quiz 12easy Docker Swarm - Why orchestration matters - Quiz 4medium Docker Swarm - Rolling updates - Quiz 5medium Docker in CI/CD - Why Docker in CI/CD matters - Quiz 13medium Docker in CI/CD - GitHub Actions with Docker - Quiz 12easy Docker in CI/CD - GitLab CI with Docker - Quiz 12easy Image Optimization - Why image optimization matters - Quiz 3easy Image Optimization - Squashing layers - Quiz 2easy Logging and Monitoring - Alert setup for container health - Quiz 14medium