Infrastructure as Code from fundamentals to production modules.
Every production incident starts with the same three questions: what changed, what is failing, and what is the blast radius. This chapter builds the mental model you use before touching a single command.
$ kubectl get pods -A --field-selector status.phase!=Running $ journalctl -u kubelet -n 100 --no-pager
Follow the guided lab to reproduce a real outage in a disposable environment, then walk through the exact diagnostic path an on-call engineer would take.
$ kubectl get pods -A --field-selector status.phase!=Running $ journalctl -u kubelet -n 100 --no-pager
Get all 150+ pages, the searchable PDF and the online reader in the members area.