How do you diagnose and fix a Kubernetes OOMKilled application?
Tests cgroup enforcement versus scheduling. A strong answer verifies OOMKilled, compares limits to usage, then rightsizes requests to baseline and limits with headroom. Red flag: confusing requests with caps or blindly raising limits.
Tests whether you know Kubernetes limits are cgroup hard caps enforced by the kernel OOM killer while requests only affect scheduling and node accounting. A strong answer confirms OOMKilled in pod status and events, correlates its working set against the limit via metrics or kubectl top, then rightsizes requests to baseline and limits with headroom while respecting QoS class. Red flag: conflating requests with runtime caps, or reflexively raising limits without distinguishing leaks from spikes.
Read the original → kubernetes.io
- #kubernetes
- #resource-management
- #oomkilled
- #troubleshooting
- #cgroup
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.