What is OOMKilled?
A Kubernetes container termination reason when a container exceeds its memory limit.
OOMKilled (Out of Memory Killed) is the container exit reason when the Linux kernel's OOM (Out Of Memory) killer terminates a process because it exceeded its cgroup memory limit. In Kubernetes, this happens when a container uses more memory than its spec.containers.resources.limits.memory setting. The pod restarts, but if the leak is in the code, it will OOMKill again. Fix by increasing limits, reducing memory usage, or finding the memory leak.
Deep Dive Guide
kubernetes oomkilled fix
Related Terms
More Kubernetes Terms
Admission Controller
A Kubernetes plugin that intercepts API requests before objects are persisted.
Auto Scaling
Automatically adjusting the number of compute resources based on demand.
ClusterIP
The default Kubernetes Service type that exposes a service on an internal cluster IP.
ConfigMap
A Kubernetes object for storing non-sensitive configuration data as key-value pairs.
Controller Manager
Kubernetes control plane component running control loops to maintain desired state.
CoreDNS
The default DNS server in Kubernetes clusters for service discovery.
Test your knowledge of OOMKilled and 130 other DevOps concepts