A payment container’s memory limit is 256Mi. Under a traffic spike the process allocates beyond that limit and the container exits with reason OOMKilled. What caused that termination?
Select an answer to reveal the explanation.
Short Explanation
Memory limits are a hard wall: climb over them and the kernel OOM-kills that container. CPU limits slow you down instead of staging that same kill. Check the limit and the app’s real footprint together.
Full Explanation
When a container surpasses its memory limit, the Linux OOM killer targets that cgroup and Kubernetes reports OOMKilled, typically followed by a restart according to the Pod’s restartPolicy. CPU limits cause throttling rather than OOMKilled. Distinguishing memory exhaustion from CPU pressure is essential when tuning resources for application Pods.