Managing GitOps as a Platform Service
summary
Platform teams run GitOps as a service using Argo CD or Flux and tools like Argo CD Autopilot and OCM, choosing among centralized vs distributed topologies and a hub-and-spoke control plane for resilience. Isolation options are full, partial, or none with tradeoffs: more isolation raises safety but multiplies instances and human overhead. Concrete advice: keep cluster configuration in separate Argo CD instances from team app instances, use RBAC and multi‑tenant patterns, and bootstrap GitOps via Git rather than manual provisioning.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:55Agenda
- 1:30GitOps as a Service
- 1:47Build vs Buy
- 2:57Platform Ops
- 3:32Developers
- 4:35Paradigms
- 5:12Developer autonomy
- 5:39Platform ownership
- 6:12Challenges
- 9:07Isolation
- 10:38Isolation models
- 11:42Safety and resource utilization
- 12:36Logical topologies
- 14:13Physical topologies
- 15:19Intuit topology
- 16:13Control plane topology
- 17:00Recommendations
- 18:11Where do you start
- 20:07Whats your best practice
- 21:17GitOps standards
- 23:36Platform engineering
- 24:55Resources
- 26:09Questions
related talks
29mThe Evolution of GitOps in Platform Engineering
21mGitOps: Where One Size Doesn't Fit All
07mIntroduction to GitOps
06mGitOps - At a Glance
27mImplementing GitOps with ArgoCD: A Practical Guide
56mNavigating the GitOps ecosystem: The principles and in-depth look at Argo and Flux
27mGitOpsify Everything: When Crossplane Meets Argo CD
01h 19mTutorial: Everything You Need To Become a GitOps Ninja