kubernetes resources ai_generated true

OOMKilled

ID: kubernetes/oomkilled

Also available as: JSON · Markdown
93%Fix Rate
95%Confidence
50Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
8 active — — —
8 active — — —

Root Cause

Container exceeded its memory limit and was killed by the OOM killer.

generic

Workarounds

  1. 93% success Profile memory usage and set appropriate resource limits 
    Use kubectl top pod to see actual memory consumption, then set limits with some headroom

    Sources: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/

  2. 90% success Check for memory leaks in the application before increasing limits 
    If memory grows linearly over time, there's a leak

Dead Ends

Common approaches that don't work:

  1. Removing memory limits entirely 85% fail

    Container can consume all node memory and affect other pods

  2. Setting memory limit to very high value 65% fail

    Hides the memory leak; wastes cluster resources

Error Chain

Frequently confused with: