[Solved] You observe this event in a pod's logs: Warning OOMKilled kubelet Container "web" was terminated due to exceeding memory limit What is the most probable cause of the pod restarting? | Kubernetes

Kubernetes - Troubleshooting

You observe this event in a pod's logs:

Warning  OOMKilled  kubelet  Container "web" was terminated due to exceeding memory limit

What is the most probable cause of the pod restarting?

AThe container crashed due to an application error

BThe container exceeded its configured memory limit and was killed by the system

CThe pod was deleted manually by an administrator

DThe container image failed to download

Step-by-Step Solution

Solution:

Step 1: Analyze event message
The event clearly states the container was terminated due to memory limit exceeded.
Step 2: Understand restart cause
When a container is OOMKilled, Kubernetes restarts it automatically unless configured otherwise.
Final Answer:
The container exceeded its configured memory limit and was killed by the system -> Option B
Quick Check:
OOMKilled event means memory limit breach [OK]

Quick Trick: OOMKilled event means memory limit exceeded [OK]

Common Mistakes:

Master "Troubleshooting" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

You observe this event in a pod's logs: