GitOps at Scale: Why Your Hub-and-Spoke Architecture is a Security Risk
summary
Centralized Hub‑and‑Spoke GitOps creates a single God-mode superuser credentials risk and runs into scaling limits: Argo CD hubs begin failing when caches hit roughly 15–20k objects, while the agent‑based Sveltos setup demos managing ~10,000 applications across ~250 clusters. The demo shows a pull/agent model that eliminates inbound access, keeps rendered manifests stored as CRDs on the hub for agents to fetch, templates private Helm charts server‑side to avoid leaking chart creds, and reports status back so the hub still sees health without direct cluster access.
AI-written summary · about
chapters (11)
- 0:00Introduction and presenters
- 1:04GitOps architectures overview
- 3:52Hub-and-spoke security risks
- 7:21Why hub-and-spoke is popular
- 8:23Central management with catalogs
- 9:50Scaling challenges for hubs
- 12:20Push vs pull modes explained
- 16:15Pull mode for firewalled clusters
- 19:21Live demo setup and walkthrough
- 23:55Recap of challenges and trade-offs
- 25:43Q&A session
related talks
29mThe Evolution of GitOps in Platform Engineering
29mTales from the Branches: GitOps in the Real World
23mScale GitOps With the Argo CD Agent and Open Cluster Management
32mLessons learnt from implementing GitOps and Continuous Delivery at scale
26mGitOps: yea or nay?
15mGitOps in the Real World: Opportunities for Developer Experience Improvement
29mWhen GitOps Becomes the Bottleneck: Scaling Argo CD for High-Churn Platforms
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes