Kubernetes API Server Watch Mechanism and the Informer Pattern

Almost every component of the Kubernetes control plane runs on top of a Watch connection to the API Server. Argo CD, HPA, kubelet, kube-proxy, all of them. When a Watch connection drops, controllers stall, and if they all recover at once, the API Server can go down with them.
This article walks through the internals of the Watch Cache first, then covers what happens when each part of the pipeline breaks.



