Kubernetes - Scheduling
You defined a PriorityClass with value 1000 but your pod remains pending and does not get scheduled with that priority. What is a likely cause?
You defined a PriorityClass with value 1000 but your pod remains pending and does not get scheduled with that priority. What is a likely cause?
medium📝 Troubleshoot Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Check PriorityClass usage
If the pod'spriorityClassNameis misspelled or does not match any existing PriorityClass, the pod will not get assigned that priority.Step 2: Verify PriorityClass default
PriorityClasses are not global defaults unless explicitly marked. Without correct naming, the pod won't get the intended priority.Step 3: Other options
Resource requests or admission controllers do not prevent priority assignment directly. PriorityClass values can be any integer.Final Answer:
PriorityClass not matched due to misspelling or lack of default -> Option DQuick Check:
Pod's priorityClassName must exactly match an existing PriorityClass [OK]
Quick Trick: Check priorityClassName spelling and existence [OK]
Common Mistakes:
- Assuming PriorityClass value must be above a threshold
- Ignoring pod resource requests as cause
- Believing admission controllers block priority assignment
Master "Scheduling" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes