CRE-2025-0137

Pod terminated with Exit Code 137 due to OOMKilled (memory limit exceeded)High

Impact: 6/10

Mitigation: 2/10

CRE-2025-0137View on GitHub

K8sExit CodeOut of MemoryMemoryCrash LoopReliability

Description

The container exceeded its memory limit and was killed by the kernel OOM killer.\nKubernetes reports a terminated state with Reason=OOMKilled and exitCode=137.\nThis often manifests as CrashLoopBackOff under sustained memory pressure.\n

Mitigation

- Raise memory requests/limits; add headroom for peak allocations.\n- Enable profiling and leak detection; tune GC/heap where applicable.\n- Consider Vertical Pod Autoscaler for right-sizing.\n- Watch node memory pressure and eviction thresholds.\n

References

• https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-states
• https://kubernetes.io/docs/tasks/administer-cluster/out-of-resource/