A reflection on the gap between memorizing Kubernetes architecture and truly understanding it through hands-on experience. The author recounts a production CrashLoopBackOff incident where diagram-level knowledge proved insufficient, and a senior engineer's instinctive use of `kubectl logs --previous` revealed how real understanding is built from debugging experience, not documentation. Key lessons include how ConfigMap changes propagate to pods, how liveness probes can kill healthy pods, and how DNS issues can trace back to resource-starved CoreDNS. The advice: spin up a local cluster with kind or minikube, deliberately break things, and build pattern-matching intuition before production incidents demand it.
Table of contents
I could recite the architecture diagram after a week. It took me a production incident to actually understand what any of it meant.What “knowing” actually gets youWhat understanding actually looks likeThe pattern I noticed after thatWhat I’d tell someone starting out132.2K Impressions12 Comments