Pod CrashLoop from OOMKill

critical

Resource ContentionUpdated Jun 27, 2025

Pods enter CrashLoopBackOff when containers are repeatedly killed by OOM (Out of Memory) killer, indicating memory limits are too restrictive or memory leaks exist.

Sources

Proactive monitoring best practices for Azure Kubernetes Service (AKS) - Azure Kubernetes Servicelearn.microsoft.com

Troubleshoot memory saturation in AKS clusters - Azurelearn.microsoft.com

Technologies:

Azure AKSSymptoms of this issue are visible in Azure AKS metrics and logs

KubernetesThe root cause of this issue originates in Kubernetes

How to detect:

Alert when KubePodCrashLooping fires AND container termination reason is OOMKilled OR memory working set approaches memory limit.

Recommended action:

Use Inspektor Gadget to identify memory-consuming processes within pods. Increase memory limits if legitimate usage, or investigate memory leaks. Set appropriate memory requests to ensure QoS class assignment.