Empowering Developers with Self-Serve IaC Using GitOps Principles
summary
AppsFlyer runs 400 engineers, 850+ microservices, 60+ Kafka clusters and thousands of cloud resources and moves from platform bottlenecks to self-serve by combining Flux + Kubernetes + Terraform and a custom tool called terracrust auto-generates client modules. terracrust hides mandatory fields and outputs main/locals/variables so developers use two-line module calls; platform maintains one layer instead of two, 70 modules with ~170 vars become consumable, velocity and correctness measurably improve.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 1:50Platform team mission and scale
- 4:01Terraform challenges and initial approach
- 6:08Problems with multi-layer Terraform modules
- 7:54Solution goals and facade pattern
- 8:38Introducing Terracrust tool
- 10:43Developer experience with Terracrust
- 11:46Results and project summary
related talks
29mWe Have Always Done It This Way! Now Let’s Try Something Completely Different
35mPanel: GitOps User Stories
29mAccelerating GitOps Adoption with Flux
43mHow GitOps Enabled Us to Answer an Unanswerable Question
43mHow GitOps Enabled Us to Answer an Unanswerable Question
16mWant to extend GitOps to Infrastructure and Workloads? Here's how.
15mTerraform, GitOps & Kubernetes: manage infrastructure & aas
46mUnlocking The Tech Wonderland: Combining GitOps, Platforms, and AI