You created a PriorityClass with globalDefault: true but pods without priorityClassName still have priority 0. What is the likely cause?

medium📝 Troubleshoot Q14 of 15

Kubernetes - Production Best Practices

You created a PriorityClass with globalDefault: true but pods without priorityClassName still have priority 0. What is the likely cause?

AThe PriorityClass value is set to 0.

BglobalDefault only works for DaemonSets, not pods.

CPods must specify priorityClassName to get any priority.

DThe PriorityClass resource was not applied correctly.

Step-by-Step Solution

Solution:

Step 1: Understand globalDefault behavior
A PriorityClass with globalDefault: true sets the default priority for pods without a specified class.
Step 2: Check why pods have priority 0
If pods still have priority 0, likely the PriorityClass was not created or applied properly, so Kubernetes does not see it as default.
Final Answer:
The PriorityClass resource was not applied correctly. -> Option D
Quick Check:
globalDefault requires correct PriorityClass creation [OK]

Quick Trick: Check if PriorityClass resource is applied when globalDefault fails [OK]

Common Mistakes:

Master "Production Best Practices" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Kubernetes Quizzes