A Multi-Cluster, Multi-Cloud Infrastructure with GitOps at CERN
summary
CERN runs a GitOps workflow that manages the cluster underlay, base services and end-user services from one repo, using Flux and Argo CD for reconciliation and an umbrella Helm chart for base components. Cross-cloud clusters become declarative Kubernetes resources via Crossplane, with automated node pools, Thanos/Prometheus aggregation, Harbor image replication and GitLab CI runners. The estate is already >600+ clusters with >10,000 cores and a cluster can be added or removed in minutes from a couple YAML lines.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:30Why Multiple Clusters
- 4:10Clusters as Cattle
- 6:22Release Channels
- 7:45Umbrella Homechart
- 9:17GitOps Training
- 11:34Public Cloud
- 14:17Deployment
- 16:47Machine Learning
- 17:20Public Cloud Stack
- 18:18Components
- 19:14RCD
- 19:37Deployment at CERN
- 22:56Infrastructure layer
- 26:00Conclusion
- 26:54Questions
related talks
24mHosting Applications in the Real World
27mGitOpsify Everything: When Crossplane Meets Argo CD
32mManaging Helm Deployments with Gitops at CERN
15mPlatform Engineering Done Right: Safe, Secure, & Scalable Multi-Tenant GitOps
36mHow CERN empowers its users with Kubernetes and OpenShift
26mGitOps Simplified
33mKubernetes As A Service with GitOps
38mEnd User Panel: GITOPS in the Enterprise -Real World Experiences