Think of your infrastructure as code
summary
The talk argues for treating infrastructure as code to replace fragile manual runbooks with reproducible, testable deployments. It demonstrates using Terraform (modules and a module registry), CI pipelines (Jenkins, Google Cloud Build, GitHub Actions), and testing/inspection tools like KitchenCI, Terraboard and Blast Radius to declaratively apply, verify and inspect infrastructure changes so iterations become predictable no-ops.
AI-written summary · about
chapters (8)
- 0:00Infrastructure as code intro
- 3:53Why adopt IaC
- 10:14Declarative vs imperative
- 16:01Testing IaC automation
- 20:36CI/CD for IaC
- 27:55CI vs CD
- 32:08IaC catalogs innovation
- 44:03Conclusion
related talks
46mImplementing Infrastructure as Code
42mInfrastructure as Code - Lessons learned from Dev to Ops
01h 02mTools and Techniques for Infrastructure as Code
16mDeclarative Infrastructure Basics for Systems Admins
54mInfrastructure as code (anti) Patterns
27mApplication-Driven Infrastructure
33mScaling Infrastructure as Code
38mApplication-Driven Infrastructure Deployment