| 1 | If you remember three things from this walkthrough, take these. First, one spine — kube-apiserver mediates every state change; no component talks to another directly, and that constraint is the architecture. Second, one truth — etcd is the only persistent store; back it up, run an odd number, and Raft handles the rest. Third, one loop — every controller in Kubernetes is the same shape: watch the API for desired state, diff it against actual state, act to converge. Once you see that loop, you can read the source of any controller in the ecosystem, because they are all variations on it. |