Kubernetes - Troubleshooting
A pod's container is OOMKilled even though its memory limit is set to 512Mi. You want to prevent this without increasing the limit. What is the best approach?
A pod's container is OOMKilled even though its memory limit is set to 512Mi. You want to prevent this without increasing the limit. What is the best approach?
hard📝 Best Practice Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Understand memory limit and OOMKilled
The container hits the 512Mi limit and is killed. Increasing limit is not an option.Step 2: Find alternative to increasing memory
Optimizing the app to use less memory reduces usage below the limit, preventing OOMKilled.Step 3: Evaluate other options
Removing limit risks node stability, increasing CPU doesn't reduce memory, adding replicas doesn't fix memory per container.Final Answer:
Optimize the application to use less memory inside the container. -> Option BQuick Check:
Lower memory use avoids OOMKilled without raising limit [OK]
Quick Trick: Reduce app memory use to avoid OOMKilled without raising limit [OK]
Common Mistakes:
- Removing memory limits causing node crashes
- Increasing CPU expecting memory fix
- Adding replicas without fixing memory use
Master "Troubleshooting" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes