Debugging a Pod in CrashLoopBackOff
WHAT IT TESTS: Practical Pod debugging instinct. OUTLINE: kubectl describe pod for events, restarts, and last state; kubectl logs (with --previous) for the crashed container's output.
WHAT IT TESTS: Whether you debug methodically from cluster signals rather than guessing. ANSWER OUTLINE: First kubectl describe pod NAME to read Events, restart count, exit codes, and the container's Last State and Reason. Second kubectl logs NAME, and crucially kubectl logs NAME --previous to capture stdout from the container that just crashed, since the live container may be too short-lived. Together these reveal config errors, missing dependencies, or failing startup commands.
Read the original → interview
- #kubernetes
- #debugging
- #crashloopbackoff
- #kubectl
- #logs
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.