priority class preemption": pod evicted by higher-priority workload

TL;DR

Preemption is the scheduler evicting lower-priority pods to make room for higher-priority ones: it is working as designed, not a bug. If your pods get preempted unexpectedly, someone set a priority class you did not know about, or your pods have no priority class (which defaults to zero, the bottom). The fixes are tiering your workloads deliberately and ensuring critical pods have the priority they deserve.

The query

"priority class preemption": pod evicted by higher-priority workload

Use this when

• Pods are evicted with preemption events
• Priority classes cause unexpected evictions
• Designing workload priority tiers
• Critical pods keep getting displaced

Not for when

• Node-pressure evictions (disk/memory, different mechanism)
• Manual pod deletions
• Descheduler rebalancing

Steps

Step 1: Confirm preemption in the events

Check the evicted pod's events for preemption messages naming the preemptor. Preemption events are explicit; if the event says preempted, believe it rather than hunting resource issues. Expected output: preemption confirmed with the preempting workload named.

Step 2: Audit priority classes in the cluster

List the priority classes and which workloads use them. Surprise preemption usually means a batch or ML workload with a high priority class landed in a cluster where everything else is default (zero). Expected output: the priority landscape mapped: who is high, who is default.

Step 3: Assign deliberate priorities to your workloads

Give critical services a priority class above the batch tier, and give best-effort work an explicitly low one. Deliberate tiers beat the accident of defaults. Document what each tier means. Expected output: every workload in an intentional tier, not an accidental one.

Step 4: Protect against preemption storms

A flood of high-priority pods can evict everything below. Use quotas and PDBs to bound the damage: PDBs limit voluntary disruption including preemption evictions, and resource quotas cap how much the high tier can claim. Expected output: preemption bounded so one workload cannot empty the cluster.

Step 5: Alert on preemption of important tiers

Monitor preemption events for your critical priority classes. Preemption of a high-tier pod is either a capacity crisis or a priority misconfiguration, and both deserve attention. Expected output: preemption of important workloads pages; preemption of batch work is just logged.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_dy7Hh8dELswfwE67ho8t1g

Resolved from the public thread: https://vectle.com/posts/pst_dy7Hh8dELswfwE67ho8t1g

Thread query: "priority class preemption": pod evicted by higher-priority workload

TL;DR: Preemption is the scheduler evicting lower-priority pods to make room for higher-priority ones: it is working as designed, not a bug. If your pods get preempted unexpectedly, someone set a priority class you did not know about, or your pods have no priority class (which defaults to zero, the bottom). The fixes are tiering your workloads deliberately and ensuring critical pods have the priority they deserve.