OOMKilled containers in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Identify the cause of OOMKilled status

You run kubectl get pods and see a pod with status OOMKilled. What does this status mean?

A The pod was terminated because it used more memory than its limit.

B The pod was restarted due to a network failure.

C The pod completed successfully and exited normally.

D The pod was deleted manually by the user.

💡 Hint

Think about what OOM stands for in computing.

OOMKilled means the pod was killed by the system because it used more memory than allowed by its limit.

❓ Troubleshoot

intermediate

Diagnose memory limits causing OOMKilled

You have a pod that keeps restarting with OOMKilled status. Which command helps you check the memory limits set on the pod?

A kubectl describe pod <pod-name>

B kubectl logs <pod-name>

C kubectl get nodes

D kubectl exec <pod-name> -- free -m

💡 Hint

Look for resource limits in pod details.

kubectl describe pod shows detailed pod info including memory limits and usage events.

❓ Configuration

advanced

Correct memory limit configuration to avoid OOMKilled

Which YAML snippet correctly sets a memory limit of 512Mi to prevent OOMKilled errors?

Kubernetes

apiVersion: v1
kind: Pod
metadata:
  name: example-pod
spec:
  containers:
  - name: example-container
    image: nginx
    resources:

A

      requests:
        memory: 512

B

      limits:
        memory: "512Mi"

C

      limits:
        memory: 512

D

      requests:
        memory: "512Mi"

💡 Hint

Memory limits must include units and be under 'limits'.

Memory limits must be set under limits with units like Mi to be valid.

✅ Best Practice

advanced

Best practice to prevent OOMKilled in production pods

What is the best practice to avoid OOMKilled errors in production Kubernetes pods?

A Disable memory limits to let pods use unlimited memory.

B Set CPU limits only and ignore memory settings.

C Set very high memory limits without requests to avoid killing.

D Set both memory requests and limits based on real usage metrics.

💡 Hint

Think about balancing resource allocation and stability.

Setting both requests and limits based on actual usage helps the scheduler and prevents OOMKilled.

🔀 Workflow

expert

Sequence to troubleshoot OOMKilled pod

Arrange the steps in the correct order to troubleshoot an OOMKilled pod:

A 3,1,2,4

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Start with pod status, then check config, then logs, then fix.

First check pod events to confirm OOMKilled, then inspect resource limits, then logs for clues, finally adjust limits.

Practice

1. What does it mean when a Kubernetes container status shows OOMKilled?

easy

A. The container was deleted manually by the user.

B. The container was restarted due to a network failure.

C. The container completed its task successfully.

D. The container was stopped because it used more memory than allowed.

Solution

1. Step 1: Understand OOMKilled meaning

   OOMKilled means Out Of Memory Killed, which happens when a container uses more memory than its limit.

2. Step 2: Relate to container status

   When a container exceeds its memory limit, Kubernetes stops it to protect the system.

3. Final Answer:

   The container was stopped because it used more memory than allowed. -> Option D

4. Quick Check:

   OOMKilled = Memory limit exceeded [OK]

Hint: OOMKilled means container used too much memory [OK]

Common Mistakes:

• Confusing OOMKilled with network errors
• Thinking OOMKilled means container finished normally
• Assuming OOMKilled is a manual stop

2. Which kubectl command helps you check why a pod's container was OOMKilled?

easy

A. kubectl get pods --all-namespaces

B. kubectl logs <pod-name>

C. kubectl describe pod <pod-name>

D. kubectl exec <pod-name> -- top

Solution

1. Step 1: Identify command to get pod details

   kubectl describe pod <pod-name> shows detailed pod info including container status and reasons for restarts.

2. Step 2: Confirm OOMKilled reason visibility

   This command shows events and container states, including if a container was OOMKilled.

3. Final Answer:

   kubectl describe pod <pod-name> -> Option C

4. Quick Check:

   Describe pod shows OOMKilled reason [OK]

Hint: Use 'kubectl describe pod' to see OOMKilled details [OK]

Common Mistakes:

• Using 'kubectl get pods' which lacks detailed reason
• Checking logs which may not show OOMKilled cause
• Running exec commands which don't show pod status

3. Given this pod description snippet, what caused the container to stop?

State: Terminated
Reason: OOMKilled
Exit Code: 137

medium

A. The container was killed because it used too much memory.

B. The container ran out of CPU resources.

C. The container was terminated due to a manual stop.

D. The container crashed due to a software error.

Solution

1. Step 1: Analyze the Reason field

   The Reason is 'OOMKilled', which means the container was killed because it exceeded memory limits.

2. Step 2: Understand Exit Code 137

   Exit code 137 means the process was killed by signal 9 (SIGKILL), typical for OOMKilled events.

3. Final Answer:

   The container was killed because it used too much memory. -> Option A

4. Quick Check:

   Reason OOMKilled + Exit 137 = Memory kill [OK]

Hint: Exit code 137 with OOMKilled means memory limit exceeded [OK]

Common Mistakes:

• Confusing CPU limits with memory limits
• Assuming manual stop without checking reason
• Thinking software error caused termination

4. You see a pod's container repeatedly OOMKilled. Which change fixes this issue?

medium

A. Increase the container's memory limit in the pod spec.

B. Decrease the container's CPU limit in the pod spec.

C. Remove the memory limit from the pod spec.

D. Restart the pod manually every time it OOMKills.

Solution

1. Step 1: Identify cause of repeated OOMKilled

   Repeated OOMKilled means the container needs more memory than allowed.

2. Step 2: Choose proper fix

   Increasing the memory limit lets the container use more memory and prevents OOMKilled.

3. Final Answer:

   Increase the container's memory limit in the pod spec. -> Option A

4. Quick Check:

   More memory limit stops OOMKilled [OK]

Hint: Raise memory limit to stop OOMKilled repeats [OK]

Common Mistakes:

• Lowering CPU limit which doesn't affect memory
• Removing memory limit causing instability
• Relying on manual restarts instead of fixing limits

5. 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

A. Increase the CPU limit to speed up processing.

B. Optimize the application to use less memory inside the container.

C. Remove the memory limit to avoid OOMKilled.

D. Add more replicas of the pod to distribute load.

Solution

1. Step 1: Understand memory limit and OOMKilled

   The container hits the 512Mi limit and is killed. Increasing limit is not an option.

2. Step 2: Find alternative to increasing memory

   Optimizing the app to use less memory reduces usage below the limit, preventing OOMKilled.

3. Step 3: Evaluate other options

   Removing limit risks node stability, increasing CPU doesn't reduce memory, adding replicas doesn't fix memory per container.

4. Final Answer:

   Optimize the application to use less memory inside the container. -> Option B

5. Quick Check:

   Lower memory use avoids OOMKilled without raising limit [OK]

Hint: 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