Bird
0
0

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

medium📝 Command Output Q5 of 15
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:
  1. Step 1: Identify OOMKilled signature

    The typical output for an OOMKilled container includes 'Reason: OOMKilled' and exit code 137.
  2. Step 2: Differentiate from other states

    Running or Completed states do not indicate OOMKilled; CrashLoopBackOff is a different error.
  3. Final Answer:

    State: Terminated\nReason: OOMKilled\nExit Code: 137 -> Option A
  4. Quick Check:

    Exit code 137 means OOMKilled [OK]
Quick Trick: Exit code 137 means OOMKilled [OK]
Common Mistakes:
  • Confusing CrashLoopBackOff with OOMKilled
  • Assuming Running state means OOMKilled
  • Ignoring exit codes in pod description

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes