Engineering the Ability to Destroy Non-Production with Terraform
summary
Claims a reproducible pipeline that adds a Terraform destroy stage to cut idle non‑production spend 40–50% and recover roughly $434B of wasted cloud cost by targeting the 76% of non‑prod that sits idle. Uses Terraform, GitHub/GitLab‑style merge‑driven pipelines, and Kubernetes for on‑demand environments, switching from long end‑to‑end CI to modular, merge‑linked stages called sustainable git flow and impermanent non‑prod that automatically tear down validated environments.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 1:10Cloud waste and environmental impact
- 4:18Non-production idle workloads
- 8:29Terraform for on-demand environments
- 10:56Sustainable GitOps pipeline demo
- 13:26Modular GitOps with destroy stages
- 15:58Corporate responsibility and data centers
- 17:25Benefits of destroying non-production
related talks
44mTaming the cloud sprawl
29mWhat would you do with 8k extra hours? Turning infrastructure into a strategic advantage
27mAdvanced Multipurpose Infrastructure: A Self-Managed Cloud Environment with HashiCorp Terraform
27mCase Study: Re-Thinking Our Infrastructure Tooling
33mBuilding Automated Pipelines for Infrastructure Code with Terraform and Packer
30mProduction-Ready Infrastructure + DevOps Workflows in 5 Minutes with Terraform + GitLab
24mTerraform Best Practices
43mHow GitOps Enabled Us to Answer an Unanswerable Question