Paths/DevOps Engineer/Incident Response / Triage Under Pressure
Triage a CrashLoopBackOff
The api pod has been restarting since the last deploy. Find why it dies and write the one-line root cause your incident channel needs right now.
Validator
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- Directory ~/incident exists○
- File ~/incident/root-cause.txt names the missing environment variable○
02Walkthrough
1 of 6 revealed- 01
See the cluster state
kubectl get pods lists every pod with its status. CrashLoopBackOff means the container starts, fails, and is restarted again and again.
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