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.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full DevOps Mastery library.

Why does a container get OOMKilled even though the node it's running on has plenty of free memory?

Next Step

Continue to Why can a container show low average CPU usage in monitoring while still suffering from CPU throttling?← Back to all Kubernetes questions