Q: A pod shows `OOMKilled` in its status. What happened and how do you fix it?
OOMKilled means the container exceeded its memory limit and the kernel killed it.
Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In one of our high-traffic production clusters, our SRE team handled this incident using a standardized runbook. The interviewer is testing: Resource limits understanding.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
OOMKilled means the container exceeded its memory limit and the kernel killed it.
- Check current limits:
kubectl describe pod— look at theLimitssection. - Increase the memory limit in the deployment spec under
resources.limits.memory. - If you're unsure what the right value is, set a higher limit temporarily and monitor actual usage with
kubectl top pod.
Remediation & Permanent Safeguards
Fix:
- Long term: use VPA (Vertical Pod Autoscaler) to auto-tune resource requests and limits.
- Check current limits: kubectl describe pod — look at the Limits section.
- Increase the memory limit in the deployment spec under resources.limits.memory.
- If you're unsure what the right value is, set a higher limit temporarily and monitor actual usage...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Restarting a crashing container without examining preceding termination logs via kubectl logs --previous when configuring shows OOMKilled status Restarting the pod flushes ephemeral container runtime state, destroying vital panic stack traces and fatal initialization logs.
-
Misdiagnosing an application boot crash as a failure of aggressive liveness probes when configuring shows OOMKilled status
Liveness probes with short timeouts or high failure thresholds kill slow-starting applications repeatedly, causing false
CrashLoopBackOffloops. -
Neglecting node taints, tolerations, and resource quotas when diagnosing pods stuck in Pending when configuring shows OOMKilled status
Pods remain
Pendingwhen scheduler predicates fail;kubectl describe podreveals whether CPU/memory exhaustion or taints prevent placement. - Invoking kubectl delete pod --force --grace-period=0 indiscriminately on unready pods when configuring shows OOMKilled status Forced deletion bypasses kubelet cleanup and can cause multi-attach errors on PersistentVolumes (PVs) or split-brain on stateful workloads.