Demo: a crash-looping pod, diagnosed
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
diagnose a broken deployment from evidence. Prepares the assessment debugging exercise.
Draft outline details
Step by step
kubectl get podsshowsordersinCrashLoopBackOff.kubectl describe podshows restarts and the last state; events show no image problem.kubectl logs --previousreveals a missing configuration value (database URL).- Planned mistake: raise memory limits as a guess because the pod "keeps dying". Fix: read the exit reason first; the exit code and logs point to configuration, not memory.
- Correct the ConfigMap, roll the Deployment, confirm readiness, and write one line for the runbook.
Check your understanding
What should you read before changing limits?
Show answer
The last state reason, exit code, and previous logs.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.