How GitOps Enabled Us to Answer an Unanswerable Question
summary
Answer: a reproducible rebuild from zero using Git as source of truth, Terraform modules and Terraform roots to repave accounts, Kubernetes clusters on EKS, image automation with Flux and image policies, PR-driven Terraform via Atlantis, secrets encrypted with SOPs, and automated compliance checks with fugue regular. Deployment frequency rises to 10× daily, lead time drops from days to minutes, MTTR falls ~72%, and full-account recovery proves possible by regular tear-downs and rebuilds.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:48System perspectives
- 3:11Entering inherited chaos
- 5:40Resistance to identity theft
- 6:44Awakening moment
- 7:25Defining strategy
- 8:28Implementation and developer experience
- 13:43Managing secrets with SOPS and Flux
- 15:27Standardizing deployments
- 17:13Automating image updates with Flux
- 20:03Testing and taxonomy importance
- 21:08Validating Kubernetes API changes
- 22:11Big picture overview
- 23:37Culture in systems
- 24:21Transformation results
- 26:04Emotional journey
- 28:51Find your unanswerable question
- 29:53Call for collaboration
- 30:34Q&A
related talks
43mHow GitOps Enabled Us to Answer an Unanswerable Question
35mGitOps - Operations by Pull Request
47mGitOps - Using Git as your source of truth for build, deploy and observability
23mA Tall Tale of GitOps
35mPanel: GitOps User Stories
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
35mApproach to GitOps — Achievements, Mistakes and Lessons Learned
26mGitOps Lifecycle Management