GitOps: Where One Size Doesn't Fit All
summary
Claims that one GitOps pattern fits all are false; discovery uncovers which parts to centralize and which to hand to teams. Use metric-based process mapping and empathy maps to find bottlenecks, run a Team Topologies four-quadrant alignment, then prototype with Argo CD, golden Helm charts, and simple pipelines. Built an onboarding automation that provisions per-team Argo CD instances and preconfigured GitOps repos; it reduces developer cognitive load, speeds first-day deployments, and scales when teams contribute back.
AI-written summary · about
chapters (7)
- 0:00GitOps and platform engineering
- 1:50Platform engineering evolution
- 5:01Developer needs discovery
- 8:55Platform expectations
- 12:10Building GitOps services
- 17:24Preconfigured GitOps tools
- 19:54GitOps adoption summary
related talks
28mManaging GitOps as a Platform Service
06mGitOps - At a Glance
15mGitOps Use Cases & Best Practices Com...
30mThe Objectives And The Principles Behind GitOps
13mHow GitOps Should I Be? Lessons from a Kinda-GitOps Environment
01h 19mTutorial: Everything You Need To Become a GitOps Ninja
29mThe Evolution of GitOps in Platform Engineering
05mLessons from a Large-Scale GitOps Implementation