[Solved] When running kubectl describe pod mypod, which output indicates the container was OOMKilled? — Ans: State: Terminated\nReason: OOMKilled\nExit Code: 137 | Kubernetes

Kubernetes - Troubleshooting

When running kubectl describe pod mypod, which output indicates the container was OOMKilled?

AState: Terminated\nReason: OOMKilled\nExit Code: 137

BState: Running\nReady: True

CState: Waiting\nReason: CrashLoopBackOff

DState: Terminated\nReason: Completed\nExit Code: 0

Step-by-Step Solution

Solution:

Step 1: Identify OOMKilled signature
The typical output for an OOMKilled container includes 'Reason: OOMKilled' and exit code 137.
Step 2: Differentiate from other states
Running or Completed states do not indicate OOMKilled; CrashLoopBackOff is a different error.
Final Answer:
State: Terminated\nReason: OOMKilled\nExit Code: 137 -> Option A
Quick Check:
Exit code 137 means OOMKilled [OK]

Quick Trick: Exit code 137 means OOMKilled [OK]

Common Mistakes:

Master "Troubleshooting" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

When running kubectl describe pod mypod, which output indicates the container was OOMKilled?