How GitOps Enabled Us to Answer an Unanswerable Question
summary
A bank team proves an unanswerable question by building a GitOps pipeline that actually works: Terraform modules and Terraform roots let teams repave infrastructure from scratch, Kubernetes hosts platform workloads, secrets use sops, and image and repo automation run via Flux and Atlantis. The self‑service platform grows from 20 to 50 developers, deployment frequency jumps from weeks to ~10 times daily, lead time falls from days to minutes, MTTR drops ~72%, and full account rebuilds complete in hours.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:48System perspectives
- 3:11Inherited chaos
- 6:22Awakening moment
- 7:25Defining strategy
- 8:28Stage four implementation and developer experience
- 13:43Secrets in GitOps
- 15:27Onboarding teams
- 17:13Flux image updates
- 20:47Kubernetes API changes
- 22:11Big picture
- 23:37Culture and systems
- 24:21Transformation results
- 27:27Key takeaway
- 28:51Unanswerable question
- 30:34Q&A
related talks
43mHow GitOps Enabled Us to Answer an Unanswerable Question
35mApproach to GitOps — Achievements, Mistakes and Lessons Learned
47mGitOps - Using Git as your source of truth for build, deploy and observability
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
35mGitOps - the holy grail of devops
26mKeynote Session: GitOps as an Evolution of Kubernetes
09mThe Future of GitOps in Modern DevOps
49mGitOps, a somewhat realistic scenario on Kubernetes with Flux