Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups. The first is a training fleet. It sat at a few thousand nodes for months, then a new run landed, and it’s at fifteen thousand. Kube-apiserver starts eating memory. The second never passes a few thousand nodes and is having a much worse day. It’s an agent platform, and its objects are alive: sessions created, suspended, resumed, and destroyed thousands of times a minute, every transition a write.

The third is neither big nor fast: a platform cluster with two hundred operators installed and tens of thousands of objects that mostly just sit there, and every apiserver holds a copy of all of them. Two of those are AI workloads, and one isn’t, which is the least interesting part. They’re running out of room in three different directions, and fixing one does nothing for the others. KubeCon + CloudNativeCon is taking place in Salt Lake City from November 9 to 12. Go looking for guidance, and you find… not much. There’s plenty of advice for getting to 5,000 nodes.

Past that, or sideways from it, the internet shrugs. So you add more apiservers. It’s a documented option in kOps and the standard answer you’ll get from most people. It makes your problem worse, because every apiserver you add replicates the entire watch cache. You bought request capacity and paid for it in memory you didn’t have. None of these is a research project. Clusters well past 5,000 nodes run in production today on stock upstream components. Nobody got there with a magic fork; they got there by being deliberate about what each store holds. The scale isn’t the hard part.

The assembly instructions are missing. Ask how big a control plane needs to be and the answer comes back in nodes. That’s how the second and third clusters end up tuned for a problem they don’t have. “The scale isn’t the hard part. The assembly instructions are missing. Training and RL fleets: large, homogeneous, and the pressure is every kubelet reporting in. At 100,000 nodes with a 10-second heartbeat, liveness alone generates about 10,000 writes per second, and in our measurements lease renewals were roughly 70% of write QPS. Most of what that control plane does is nodes politely saying “still here,” forever.