Pod Killed with OOMKilled
What it means when a pod is terminated with OOMKilled, and how to decide between raising its memory limit and reducing its memory usage.
If a pod is terminated with OOMKilled, it used more memory than its limit
allowed, so it was terminated. This article explains what to do about it.
Either:
- Raise
resources.limits.memoryin your Component configuration, or - Reduce the application's memory usage — a limit that keeps needing to grow is
usually a leak rather than a sizing problem.
Enabling VPA in recommender mode first will tell you which of the two you are
looking at — see
Workload Resources and Health Checks.
Still having issues?
Raise a request with the namespace, the Component name, the pod status, and what
you have already tried.
Related articles
- Workload Resources and Health Checks — resource requests, limits and health checks
- Pod Keeps Restarting (CrashLoopBackOff) — the pod starts but then fails
- Pod Stuck in Pending (FailedScheduling) — the pod never starts at all
- Pod Restarted During Node Maintenance — a restart with no change on your side
- Troubleshooting Common Issues — find your symptom
Updated about 1 month ago
Did this page help you?