Debugging Kubernetes OOMKilled: A Step-by-Step Guide
The Dreaded OOMKilled $ kubectl describe pod api-service-7f8d9c-abc12 ... State: Terminated Reason: OOMKilled Exit Code: 137 Your container got killed because it used more memory than its limit. Sounds simple. Debugging it is not. # Check pod events kubectl get events --field-selector involved
ORIGINAL SOURCE →via Dev.to
ADVERTISEMENT
⚡ STAY AHEAD
Events like this, convergence-verified across 689 sources, land in your inbox every Sunday. Free.
GET THE SUNDAY BRIEFING →RELATED · tech
- [TECH] Launch: Ariane 64 | Amazon Leo (LE-02)
- [TECH] Launch: Atlas V 551 | Amazon Leo (LA-06)
- [TECH] Launch: Falcon Heavy | ViaSat-3 F3 (ViaSat-3 Asia-Pacific)
- [TECH] Launch: Falcon 9 Block 5 | Starlink Group 17-16
- [TECH] Launch: Soyuz 2.1a | Progress MS-34 (95P)
- [TECH] Launch: Long March 6 | Unknown Payload