Paths/DevOps Engineer/Kubernetes / Debugging Workloads
Diagnose a Crashing Pod
A Pod called api in this cluster is stuck in CrashLoopBackOff. Find out why from its logs, identify the missing piece, and record it. Failure is part of the curriculum.
Validator
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/report/crash.txt exists naming the missing environment variable○
02Walkthrough
1 of 6 revealed- 01
See the Pod state
kubectl get pods shows api in CrashLoopBackOff — Kubernetes restarted it repeatedly and is now backing off. The state says the container exits; not why.
kubectl get pods - 5 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — kubernetes 1.30 (kind)
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list