0 of 24 chapters written · 3 levels planned
Kubernetes
Orchestration, at the object level
Not written yet
Pods, Deployments and Services first, then the networking, storage and RBAC that make a cluster production-grade — and the operator/GitOps layer on top. Beginner through advanced, laid out the same way as the rest of the shelf.
The plan
- chapters planned
- 24
- levels
- 3
- chapters written
- 0
What is planned, level by level
Every stop below is an outline for now. Open one to see what it will cover.
Beginner
“I can run a working app on a cluster.”
7 sections
- soon
- soon
- soon
Intermediate
“I can run a real cluster.”
9 sections
- soon
- soon
Advanced
“I can reason about the control plane.”
8 sections
- soon
- soon
- soon
- soon
Meanwhile
Nothing here is written yet, but these are.
Three honest notes
This assumes Docker already — it starts at "why one container isn't enough," not at what a container is. If that's shaky, the Docker topic on this shelf comes first.
Helm shows up in intermediate, not beginner, on purpose — templating manifests only makes sense once you've felt the pain of writing several by hand.
Service meshes and GitOps are the deepest, most infrastructure-team layer — most application developers on a cluster never operate them directly, but the advanced tier doesn't skip them.