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.
#Kubernetes #Troubleshooting & Debugging #L2 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""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.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
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.
2️⃣
Remediation & Permanent Safeguards
Fix:
- Long term: use VPA (Vertical Pod Autoscaler) to auto-tune resource requests and limits.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Check current limits: kubectl describe pod — look at the Limits section.."
⚡ 60-Second Elevator Pitch Talking Points
- 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...
Advertisement