CrashLoopBackoff, Pending, FailedMount and Friends: Debugging Common Kubernetes Cluster
summary
Step‑by‑step debugging workflow that shows how to get actionable data with kubectl logs and get events, when to SSH into nodes for journalctl or container runtime logs, and how common failures actually manifest: wrong image pull secrets, CrashLoopBackoff from a bad command, Pending from no PV or autoscaler limits, FailedMount PVC binding errors and RBAC denials, DNS or network policy blocking service discovery. Live demos use Weave Scope, kubectl apply/describe, deleting and reapplying DaemonSets and Deployments to prove fixes.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:09Take a deep breath
- 3:07Let's talk about..
- 4:39Container logs
- 5:21Debugging containers
- 6:49Know what normal abnormal behavior looks like
- 7:20Cluster networking issues
- 8:19Pod startup issues
- 8:56Service discovery issues
- 10:09Access control issues
- 15:14Post-deployment
- 18:47Kubernetes Slack
- 19:06Look within
- 20:29We've just scratched the surface here
- 21:37Don't Fall for Impostor Syndrome
- 34:32Grateful Appreciation To
related talks
45mTroubleshooting containerized applications
36mKubernetes Confessions: Real Mistakes We’ve All Made (and What They Teach Us)
35mKubectl Said What?
45mWhat I Learnt Fixing 50+ Broken Kubernetes Clusters
34mReading 100+ Kubernetes Post-Mortems - lessons learned
24mDebugging at Scale in Production - Deep into your Containers
30mManaging Kubernetes Without Losing Your Cool
25mDebugging at Scale in Production with kubectl debug