Phase
Phase 1
Why operators exist, the control loop, Kubebuilder scaffolding, and your first reconciliation — foundations before real controller logic.
4 published · 0 upcoming
- Part 1Published
Why Kubernetes Operators Exist — The Problem They Actually Solve
Before we write a single line of controller code, we need to feel the pain that makes operators worth the complexity. This post builds the wrong system first — on purpose.
- Part 2Published
The Kubernetes Control Loop — Explained by Building One
Before touching Kubebuilder, we build a working Kubernetes-style control loop from scratch in Go — no k8s libraries. Every component is explicit, observable, and directly maps to what Kubebuilder generates.
- Part 3Published
Kubebuilder From Zero — Scaffold, Structure, and Your First CRD
We install Kubebuilder, run kubebuilder init and create api, then walk through every generated file line by line — with the Blog 2 control loop mental model as the map.
- Part 4Published
Your First Reconciliation Loop — Line by Line
We fill in the empty Reconcile() stub from Blog 3 with a complete, production-aware implementation — fetching desired state, observing actual state, provisioning a StatefulSet, updating status conditions, and handling every return path correctly.