Pod Killed with OOMKilled

If a pod is terminated with OOMKilled, it used more memory than its limit allowed. This article explains what to do about it.

The pod used more memory than its limit allowed, so it was terminated. Either:

1. Raise resources.limits.memory in your Component configuration, or
2. 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.

Still having issues?

Raise a request with the namespace, the Component name, the pod status, and what
you have already tried.

Related articles

• Workload Management — resource requests, limits and health checks
• Troubleshooting Common Issues — find your symptom