Fixing OOMKilled Exit Code 137: A kubectl 30-Second Diagnosis and 5-Minute Recovery Runbook
Did your Pod die with OOMKilled exit code 137? In 30 seconds, use kubectl describe, jsonpath, and dmesg to tell whether it exceeded the container limit or the node was under memory pressure—then recover in 5 minutes with copy-paste commands
Jun 28
Solving CrashLoopBackOff: Diagnosing 7 Causes of Infinite Pod Restarts
If a Pod keeps restarting with CrashLoopBackOff, narrow the cause in a minute with kubectl describe and logs --previous. Diagnostic commands and YAML fix examples for seven causes, including OOMKilled (Exit 137), missing secrets, and livene
Jun 12