Case Study: Re-Thinking Our Infrastructure Tooling
summary
Company replaces a nine year old Python templating layer with a Terraform templating engine that generates an individual infra-as-code repo per customer so changes can be applied across dozens to hundreds of clusters without interactive logins. Goal is faster sweeping upgrades, drift reduction, and clear repo export for customer offboarding. Implementation is iterative and team-driven, about 75–80% implemented, uses Terraform to avoid new language upskilling, and survives a HashiCorp licensing risk by keeping tooling choices abstract.
AI-written summary · about
chapters (10)
- 0:00Introduction to the Case Study
- 0:50Challenges in Managing Kubernetes Infrastructure
- 2:15Rethinking Infrastructure Management
- 2:48Reasons for Rewriting Infrastructure Tooling
- 5:09Process of Redesigning the Tooling
- 11:31Evaluating Potential Solutions
- 17:14Choosing the Final Solution
- 18:26Implementation and Team Involvement
- 19:38Tips for Re-architecting Tooling Stack
- 21:59Conclusion and Q&A
related talks
27mCase Study: Re-Thinking Our Infrastructure Tooling
44mTaming the cloud sprawl
22mLessons Learned from Scaling Infrastructure as Code
25mRebuilding Infrastructure (as Code)
29mBreaking Down the TofuLith. How We Reduced Lead Times for Multi-Tenant Infra Changes...
46mThink of your infrastructure as code
14mHow Global Discovery tribe approaches Infrastructure Changes at scale
33mScaling Infrastructure as Code