Kubernetes scalability conversations usually start with the obvious stuff. How many nodes? How many pods? How large is the cluster? How much etcd pain can one organization spiritually endure before someone says “maybe we should split this thing” in a meeting and everyone pretends they were already thinking it? Fair questions. But I think Kubernetes v1.36 server-side sharded list and watch points at a quieter, more interesting problem: the control plane is becoming a data distribution system, and the hard part is no longer only storing objects. It is feeding every client that wants to continuously know what changed. That sounds boring. Good. Boring infrastructure primitives are where the real architecture leaks out. watch was always the magic trick One of the reasons Kubernetes feels so powerful is the watch model. Controllers do not constantly ask, “hey, did anything happen?” like an anxious intern refreshing a dashboard. They list the current state, then watch for changes.…