vCluster reposted this
At what point does a GitOps hub become the bottleneck when managing 15,000 Kubernetes clusters in a Hub-and-Spoke architecture? That question came from a real kubara community request, so we built a test model try to predict the behavior instead of guessing. TL;DR: We tested GitOps fleet management with Argo CD, vCluster, kubara, and Project Sveltos. In our setup, Argo CD’s application controller started hitting OOM kills at around 15k–20k cached objects per hub. Hydrated manifests helped, tuning helped only partially, and Sveltos handled addon-style rollout patterns at a fraction of the memory: around 2 GB compared to around 21 GB with Argo CD. The main lesson: at very large scale, architecture matters more than tuning. And combining GitOps engines is a real multiplier for what you can achieve with Open Source. Cost was also a key part of the test: running this at full target scale would have cost roughly €1.2M. With support from STACKIT, and by using vCluster to design realistic peak scenarios, we brought the cost down to around €120K while still testing 1,000 clusters and up to 5,000 heavy Applications. More in the blog post: https://lnkd.in/esMf5Qxd --- P.S. This is an honest reflection based on weeks of work. We simply wanted to share with the community what we tested, what we learned, and what we saw along the way.