When GitOps Is Not Enough
summary
Roche manages potentially thousands of near-identical Kubernetes clusters and finds single-repo GitOps with Flux and Kustomize fails for per-cluster customizations, canary updates, access separation and geo-local Git hosting. The solution is one Git repo per cluster plus template-driven provisioning — dubbed MegOps (=Meta GitOps) — implemented with a new open-source service foxops (Python, Jinja2, API + DB). foxops creates versioned repo “incarnations,” applies template updates via merge requests with optional auto-merge, and the demo shows repo init and a successful template rollout.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:04Roche and infrastructure team
- 3:50Initial GitOps application
- 5:14Challenges with single repo
- 6:58One repo per cluster
- 8:22MegOps and FoxOps tool
- 9:48FoxOps templates and incarnations
- 11:35Demo overview
- 12:19Demo setup and structure
- 15:05New customer infrastructure
- 16:52Updating customer instance
- 18:14FoxOps use cases
related talks
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
23mGitOps: yea or nay?
26mKeynote Session: GitOps as an Evolution of Kubernetes
06mGitOps - At a Glance
39mSoftware Rollout at Scale: Using GitOps to Scale Kubernetes Rollouts
45mGitops: The Kubernetes way
40mHow GitOps Changes Everything in CI/CD
26mGitOps Lifecycle Management