Playbook

OOMKill Discovery

Diagnose and resolve Out-Of-Memory (OOM) kills in Kubernetes.

Check pod status for 'OOMKilled' reason in 'kubectl get pods'.

Inspect 'kubectl describe pod <name>' for exit code 137.

Look for 'Out of memory: Kill process' in node dmesg or syslog.

Temporarily increase memory limits if headroom is available on the node.

Check for sudden spikes in traffic or data processing volume.

Verify if the application's heap size is correctly tuned for the container limit.

Optimize application memory usage (buffer sizes, concurrency).

Implement better memory management or switch to a more efficient runtime.

Use Vertical Pod Autoscaler (VPA) to right-size resource requests.

Find OOMKilled Pods

kubectl get pods -A | grep -i OOMKilled

Check Node OOM Events

journalctl -k | grep -i "out of memory"

Get Pod Resource Usage vs Limits

kubectl top pod <pod-name> --containers