Bird
0
0

A Pod with the nodeSelector storage=fast remains in Pending state. What is the most probable reason?

medium📝 Troubleshoot Q6 of 15
Kubernetes - Scheduling
A Pod with the nodeSelector storage=fast remains in Pending state. What is the most probable reason?
AThe Pod spec has invalid YAML syntax
BNo nodes have the label <code>storage=fast</code>
CThe Pod's container image is missing
DThe cluster has insufficient CPU resources
Step-by-Step Solution
Solution:

  1. Step 1: Understand nodeSelector behavior

    nodeSelector restricts Pod scheduling to nodes with matching labels.

  2. Step 2: Analyze Pending state cause

    If no nodes have the label storage=fast, the Pod cannot be scheduled and stays Pending.

  3. Step 3: Rule out other options

    Invalid YAML or missing images cause different errors; insufficient CPU would not specifically cause Pending due to nodeSelector.

  4. Final Answer:

    No nodes have the label storage=fast -> Option B

  5. Quick Check:

    nodeSelector requires matching node labels [OK]
Quick Trick: Pod Pending if no matching node labels [OK]
Common Mistakes:
  • Assuming Pending means image pull error
  • Ignoring node labels when troubleshooting
  • Confusing resource shortages with label mismatches

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
ConfigMaps - Updating ConfigMaps and propagation - Quiz 9hard Health Checks and Probes - Startup probe concept - Quiz 2easy Ingress - TLS termination with Ingress - Quiz 12easy Ingress - Ingress controllers (Nginx, Traefik) - Quiz 7medium Ingress - Ingress controllers (Nginx, Traefik) - Quiz 9hard Ingress - TLS termination with Ingress - Quiz 10hard Ingress - TLS termination with Ingress - Quiz 1easy Networking - DNS in Kubernetes (CoreDNS) - Quiz 1easy Persistent Storage - StatefulSet ordering and naming - Quiz 15hard Scheduling - Jobs and CronJobs for batch processing - Quiz 5medium