Why Pod priority and preemption in Kubernetes? - Purpose & Use Cases

The Big Idea

What if your most important app could always run, even when everything else is busy?

The Scenario

Imagine you have many tasks running on your computer, but some are more important than others. You try to run them all at once, but your computer gets slow and some important tasks don't get enough attention.

In Kubernetes, this is like running many pods (small apps) on limited servers without telling the system which ones matter most.

The Problem

Without telling Kubernetes which pods are more important, all pods compete equally for resources. This can cause important pods to wait or fail when resources are tight.

Manually stopping less important pods to free resources is slow, error-prone, and can cause downtime.

The Solution

Pod priority and preemption lets you mark pods with importance levels. When resources run low, Kubernetes automatically pauses or stops lower priority pods to make room for higher priority ones.

This keeps your critical apps running smoothly without manual intervention.

Before vs After

✗ Before

kubectl delete pod low-priority-pod
kubectl apply -f high-priority-pod.yaml

✓ After

apiVersion: scheduling.k8s.io/v1
kind: PriorityClass
metadata:
  name: high-priority
value: 1000
globalDefault: false
description: "High priority class for important pods"
---
apiVersion: v1
kind: Pod
metadata:
  name: important-pod
spec:
  priorityClassName: high-priority
  containers:
  - name: app
    image: nginx

What It Enables

You can ensure your most important applications always get the resources they need, even when the cluster is busy.

Real Life Example

In a busy online store, checkout service pods get high priority so customers can always complete purchases, while background analytics pods have lower priority and pause if needed.

Key Takeaways

Manual resource management is slow and risky.

Pod priority and preemption automate resource sharing based on importance.

This keeps critical apps running smoothly during high demand.

Practice

1. What is the main purpose of pod priority in Kubernetes?

easy

A. To decide which pods get scheduled first when resources are limited

B. To assign network policies to pods

C. To control pod security settings

D. To manage pod storage volumes

Solution

1. Step 1: Understand pod priority concept

   Pod priority is used to rank pods by importance for scheduling decisions.

2. Step 2: Identify scheduling impact

   When resources are scarce, higher priority pods are scheduled before lower priority ones.

3. Final Answer:

   To decide which pods get scheduled first when resources are limited -> Option A

4. Quick Check:

   Pod priority controls scheduling order = A [OK]

Hint: Pod priority ranks pods for scheduling under resource limits [OK]

Common Mistakes:

• Confusing priority with security or network policies
• Thinking priority controls storage or volumes
• Assuming priority affects pod runtime behavior

2. Which YAML field correctly assigns a priority class to a pod?

easy

A. spec.priority: high-priority

B. metadata.priorityClass: high-priority

C. metadata.priorityClassName: high-priority

D. spec.priorityClassName: high-priority

Solution

1. Step 1: Recall pod spec fields

   The priority class is set under the pod's spec using priorityClassName.

2. Step 2: Verify correct YAML syntax

   Correct field is spec.priorityClassName, not metadata or spec.priority.

3. Final Answer:

   spec.priorityClassName: high-priority -> Option D

4. Quick Check:

   Priority class set in spec.priorityClassName = C [OK]

Hint: Use spec.priorityClassName to assign priority class in pod YAML [OK]

Common Mistakes:

• Placing priorityClassName under metadata instead of spec
• Using spec.priority instead of priorityClassName
• Misspelling the field name

3. Given these pods with priorities: Pod A (priority 1000), Pod B (priority 500), Pod C (priority 1000). If resources are limited and only two pods can run, which pods will Kubernetes schedule?

medium

A. Pod B and Pod C

B. Pod A and Pod C

C. Pod A and Pod B

D. Pod B only

Solution

1. Step 1: Compare pod priorities

   Pod A and Pod C have priority 1000, Pod B has 500.

2. Step 2: Select highest priority pods

   Kubernetes schedules pods with highest priority first, so Pod A and Pod C run.

3. Final Answer:

   Pod A and Pod C -> Option B

4. Quick Check:

   Highest priority pods scheduled = A [OK]

Hint: Schedule pods with highest priority first when resources are limited [OK]

Common Mistakes:

• Choosing pods with lower priority over higher
• Assuming all pods run regardless of resources
• Ignoring equal priority pods

4. You created a pod with priorityClassName: "high-priority" but it is not preempting lower priority pods when scheduled. What could be the reason?

medium

A. The priority class "high-priority" is not defined in the cluster

B. Pod preemption is disabled by default in Kubernetes

C. The pod spec is missing resource requests

D. The pod is running on a node with no other pods

Solution

1. Step 1: Check priority class existence

   If the priority class "high-priority" is not defined, the pod cannot use it for preemption.

2. Step 2: Understand preemption behavior

   Preemption requires a valid priority class; missing it disables preemption.

3. Final Answer:

   The priority class "high-priority" is not defined in the cluster -> Option A

4. Quick Check:

   Undefined priority class blocks preemption = D [OK]

Hint: Ensure priority class exists before expecting preemption [OK]

Common Mistakes:

• Assuming preemption is disabled by default
• Ignoring missing resource requests impact
• Not checking node pod status

5. You have a cluster with pods of different priorities. A new pod with priority 2000 is pending due to lack of resources. How does Kubernetes handle this situation?

hard

A. It waits until resources are manually freed without preemption

B. It schedules the new pod alongside others, causing resource overcommit

C. It preempts lower priority pods to free resources for the new pod

D. It deletes the new pod automatically due to insufficient resources

Solution

1. Step 1: Understand preemption role

   When a high priority pod is pending, Kubernetes can preempt lower priority pods to free resources.

2. Step 2: Apply preemption behavior

   Kubernetes stops lower priority pods to schedule the higher priority pod if possible.

3. Final Answer:

   It preempts lower priority pods to free resources for the new pod -> Option C

4. Quick Check:

   High priority pod triggers preemption = B [OK]

Hint: High priority pods preempt lower ones to get scheduled [OK]

Common Mistakes:

• Thinking Kubernetes waits without preemption
• Assuming resource overcommit happens automatically
• Believing new pods get deleted if pending