Kubernetes, the Engineering Way

Why each piece of Kubernetes exists, not just what it does.

Most Kubernetes guides teach the resources one by one. This series starts from the problems instead: an application crashes, traffic triples, a database needs its data back. Each part asks what an engineer would need, and then shows the piece of Kubernetes that answers it.

1. Stop Memorizing Kubernetes. Start Thinking Like an Engineer. Ten questions, from "what if my app dies?" to "what if Kubernetes doesn't know my thing?", and the one idea behind all the answers: reconciliation.
2. More parts on the waySoon Each one goes deeper into a single question.