From Infrastructure as Code to Environment as Code: ...
summary
Proposes Environment as Code as a declarative layer over Terraform Helm Pulumi and Kubernetes that provisions full environments (VPC EKS Postgres S3 etc.) instead of individual resources, implements a Kubernetes operator style control plane to manage environment state with dependency graph, drift detection, plan-and-approve reconciliation, and teardown via a single flag. Claims this replaces hand‑rolled pipelines (one example hit 1,000 lines), encourages loose coupling of components, enables idempotent / immutable environment updates and GitOps promotion and visualizes environment status and costs.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:15What is Infrastructure as Code
- 5:50Challenges
- 7:42Environment as Code
- 12:30Attributes of Environment as Code
- 18:54Drift Detection
- 24:14Drift
related talks
28mFrom Infrastructure as Code to Environment as Code: Challenges scaling IaC
46mImplementing Infrastructure as Code
46mThink of your infrastructure as code
32mCode Quality and Infrastructure as Code
46mThe Rise and (Potential) Fall of Infrastructure as Code
16mDeclarative Infrastructure Basics for Systems Admins
31mHarnessing Kubernetes: The Paradigm Shift to Code‑Provisioned Clusters and Pods
05mAn Environment Per Branch with Infrastructure as Code