advancedResource Management: Requests, Limits, QoS Classes & OOMKilled
Why does a container get OOMKilled even though the node it's running on has plenty of free memory?
OOMKilled is triggered by the container exceeding its OWN configured memory limit, enforced by the kernel's cgroup memory controller — it has nothing to do with how much memory the broader node has free; a too-tight limit kills a container even on an otherwise idle node.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response