OOMKilled in Kubernetes (Requests vs Limits).
Updated Apr 28, 2026
Short answer
OOMKilled (Out of Memory) occurs when a container exceeds its defined memory limit, causing the Linux kernel to kill the process.
Deep explanation
Requests guarantee a minimum amount of resources (used by the scheduler to place the Pod). Limits define a hard maximum. If a container exceeds CPU limits, it is throttled. If it exceeds Memory limits, it is terminated (OOMKilled). Setting limits too close to requests without profiling leads to unstable deployments.
Unlock with a Pro subscription to view this section.
View pricingReal-world example
No real-world example available yet.
Unlock with a Pro subscription to view this section.
Upgrade to ProCommon mistakes
No common mistakes listed yet.
Unlock with a Pro subscription to view this section.
Upgrade to ProFollow-up questions
No follow-up questions available yet.
Unlock with a Pro subscription to view this section.
Upgrade to Pro