Bird
0
0

A pod with priorityClassName set to a non-existent PriorityClass is stuck pending. Why?

medium📝 Troubleshoot Q7 of 15
Kubernetes - Scheduling
A pod with priorityClassName set to a non-existent PriorityClass is stuck pending. Why?
APod runs but with zero CPU and memory
BPod is scheduled with default priority silently
CScheduler cannot assign priority and delays scheduling
DPod is immediately deleted by the system
Step-by-Step Solution
Solution:

  1. Step 1: Understand scheduler behavior with invalid PriorityClass

    If the PriorityClass does not exist, the scheduler cannot assign priority.

  2. Step 2: Resulting pod state

    Pod remains pending because scheduler waits for valid priority assignment.

  3. Final Answer:

    Scheduler cannot assign priority and delays scheduling -> Option C

  4. Quick Check:

    Invalid PriorityClass causes pod to stay pending [OK]
Quick Trick: Non-existent PriorityClass causes pod to stay pending [OK]
Common Mistakes:
  • Assuming pod runs with default priority
  • Thinking pod is deleted immediately
  • Believing pod runs with zero resources

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Health Checks and Probes - HTTP probe configuration - Quiz 15hard Ingress - Ingress controllers (Nginx, Traefik) - Quiz 10hard Ingress - Ingress controllers (Nginx, Traefik) - Quiz 12easy Networking - DNS in Kubernetes (CoreDNS) - Quiz 10hard Networking - Why Kubernetes networking matters - Quiz 7medium Networking - Ingress and egress rules - Quiz 10hard Scheduling - Node affinity and anti-affinity - Quiz 10hard Scheduling - DaemonSets for per-node workloads - Quiz 12easy Secrets - Why Secrets manage sensitive data - Quiz 14medium Secrets - External secret management integration - Quiz 3easy