Build · shipped

30 Days of Kubernetes (CKAD) — Day 05: Resource Requests, Limits & QoS Classes

Day 05 of the 30-day CKAD hands-on series: mastering CPU/Memory requests vs limits, OOMKilled behavior, and Pod QoS classes.

Kubernetes schedules Pods based on requests, and enforces hard ceilings via limits.


1. Requests vs. Limits

  • Requests: What kube-scheduler uses to guarantee capacity when picking a worker node.
  • Limits: The hard ceiling enforced by Linux cgroups:
    • Exceed CPU limit → Container is throttled (slows down, stays alive).
    • Exceed Memory limit → Kernel triggers OOMKilled (exit code 137).

2. Quality of Service (QoS) Classes

Kubernetes automatically assigns one of three QoS classes:

  1. Guaranteed: Every container sets both requests and limits for CPU and Memory, and requests == limits. Last to be evicted under node pressure.
  2. Burstable: At least one container has a request or limit set, without meeting Guaranteed criteria.
  3. BestEffort: No requests or limits set anywhere. First to be evicted.

3. Hands-On Lab: Day 05

In labs/k8s-30-days/day-05/:

  1. Create namespace ckad-day05.
  2. Deploy Pod guaranteed-app with cpu: "100m" and memory: "128Mi" for both requests and limits.
  3. Inspect its status.qosClass and verify with ./labs/k8s-30-days/day-05/verify.sh.

Search DivineForge