From Infrastructure as Code to Environment as Code: Challenges scaling IaC
summary
Claims that environment as code sits above Terraform/Pulumi/CloudFormation and provides a control plane that orders component runs (networking → platform → k8s → add‑ons), tracks a single environment state file, detects drift and reconciles with an approval step, and enables immutable environment replacements instead of patching. Describes pipelines requiring bespoke orchestration and extra teams, and shows a working product called Z Lifecycle that generates visuals from the environment spec and performs GitOps-style reconciliation.
AI-written summary · about
chapters (11)
- 0:00Start
- 4:29Options for Entire Environment Provisioning
- 6:02Other Challenges scaling laC
- 8:55Environment as Code
- 11:26Provision Environment
- 13:23Teardown Environment
- 13:56Ability to define Entire Environment
- 15:08Loosely Coupled
- 15:46Manage State for the entire Environment
- 23:31Drift Detection and Reconciliation
- 26:31Attributes of EaC
related talks
27mFrom Infrastructure as Code to Environment as Code: ...
32mCode Quality and Infrastructure as Code
46mImplementing Infrastructure as Code
28mInfrastructure as Code in the Real World
42mInfrastructure as Code - Lessons learned from Dev to Ops
46mThe Rise and (Potential) Fall of Infrastructure as Code
19mInfrastructure as Code: A Must Know Skill for Today's Developers
46mThink of your infrastructure as code