> When a kubelet starts up, it registers itself as a node with the API server and starts watching for pods to run. This is really great, because it means that w

> When a kubelet starts up, it registers itself as a node with the API server and starts watching for pods to run. This is really great, because it means that when we get to running a multinode cluster, we can add nodes without having to reconfigure the API server I really like the parts of this series that emphasize Kubernetes' design decisions -- it also says that all state is stored in etcd and that the API server is the only component that has access to etcd.