[Solved] A pod's container is OOMKilled despite having a memory limit set. What could be a reason? — Ans: The memory limit is too low for the container's workload | Kubernetes

Kubernetes - Troubleshooting

A pod's container is OOMKilled despite having a memory limit set. What could be a reason?

AThe container image is too large

BThe CPU limit is set too high

CThe pod has no node affinity rules

DThe memory limit is too low for the container's workload

Step-by-Step Solution

Solution:

Step 1: Understand why OOMKilled happens with limits set
If memory limit is set but container still OOMKilled, the limit is likely too low.
Step 2: Eliminate unrelated causes
CPU limits, node affinity, and image size do not directly cause OOMKilled.
Final Answer:
The memory limit is too low for the container's workload -> Option D
Quick Check:
Low memory limit causes OOMKilled despite limits [OK]

Quick Trick: OOMKilled with limits means limit is too low [OK]

Common Mistakes:

Master "Troubleshooting" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

A pod's container is OOMKilled despite having a memory limit set. What could be a reason?