Command Palette

Search for a command to run...

Hectal
Phase 6Intermediate7 of 10 in Kubernetes

Troubleshooting & Production Operations

Recognize the common failure states by name, know the exact commands that reveal why, and understand how a rollout actually rolls back when it goes wrong.

Every phase so far has covered how Kubernetes works when things go right. This phase is what to do when they don't — the specific, recognizable failure states every real cluster produces, the small set of commands that diagnose almost anything, and how updates and rollbacks actually work under the hood.

0/4 · 0%
4 topics ~56 min 7 code blocks & diagrams
Start with the first topic
1
6.1

Pod Lifecycle & Common Failure States

CrashLoopBackOff, ImagePullBackOff, and OOMKilled are specific, recognizable failure states with specific causes — learning to read them by name is the fastest path from 'something's wrong' to 'I know exactly what's wrong.'

15 min 1 diagram 1 code practice

2
6.2

The kubectl Debugging Toolkit

describe, logs, exec, port-forward, and events cover the overwhelming majority of real troubleshooting — knowing exactly which one answers which question is most of what separates fast debugging from guessing.

14 min 1 diagram 1 code practice

3
6.3

Rolling Updates & Rollbacks

A Deployment's default rolling update replaces pods gradually to avoid downtime — and if the new version turns out to be broken, rolling back to the previous working version is a single, fast command.

14 min 1 diagram 1 code practice

4
6.4

Resource Monitoring with kubectl top

kubectl top gives you real, live CPU and memory usage for nodes and pods — the fastest way to answer 'is something actually using too much' without needing a full observability stack set up.

13 min 1 code practice