# D2DO285: The Death of IaC Has Been Greatly Exaggerated

Page: https://stenobird.com/podcast/day-two-devops/d2do285-the-death-of-iac-has-been-greatly-exaggerated
Text version: https://stenobird.com/podcast/day-two-devops/d2do285-the-death-of-iac-has-been-greatly-exaggerated.md
Podcast: [Day Two DevOps](https://stenobird.com/podcast/day-two-devops)
Published: 2025-10-22T15:33:29+00:00
Episode link: https://packetpushers.net/podcasts/day-two-devops/d2do285-the-death-of-iac-has-been-greatly-exaggerated/
Audio file: https://feeds.packetpushers.net/link/20975/17191365/D2DO285B.mp3
Processing state: processed
JSON: https://stenobird.com/v1/public/podcasts/day-two-devops/episodes/d2do285-the-death-of-iac-has-been-greatly-exaggerated
Duration seconds: 2392

## Resource

Infrastructure as Code (IaC) is not dying; it is evolving to bridge the gap between static configuration and dynamic orchestration. The discussion explores why the core value of IaC remains intact despite criticisms of its complexity and state management.

## Highlights
- Main idea: IaC provides a necessary structured model for managing the full lifecycle of infrastructure, far beyond simple API wrappers
- Failure mode: Relying on simple YAML-to-API mappings lacks the expressiveness needed to handle complex, real-world infrastructure dependencies
- Practical takeaway: The future of IaC lies in convergence, where tools like Terraform and OpenTofu adopt more Kubernetes-like, reactive patterns
- Tension: There is a significant disconnect between application developers, who often avoid infrastructure definition, and DevOps engineers who manage it
- Main idea: The value of IaC is found in its ability to decouple compute and storage, allowing for scalable, modular infrastructure updates

## Topics

Infrastructure as Code, Terraform, DevOps, Cloud Infrastructure, Kubernetes, Automation, OpenTofu, State Management

## Chapters
- 1:00 — The LinkedIn Hype Cycle: A discussion on how provocative social media posts about the 'death' of popular tools drive engagement but often lack technical depth.
- 3:55 — Defining True IaC: Distinguishing between simple API automation and true Infrastructure as Code that offers high expressiveness and lifecycle management.
- 6:50 — The Limits of Declarative YAML: Analyzing why simple mapping of configuration to cloud provider APIs fails to capture the complexity of modern environments.
- 10:10 — Managing the Full Lifecycle: Why infrastructure management requires more than just initial provisioning; it requires managing state and continuous evolution.
- 15:40 — The Risks of State Management: Examining the 'abusive relationship' with tools like Terraform when state becomes difficult to manage or recover.
- 24:35 — The Kubernetes and VMware Parallel: Comparing the management of modern container orchestration to legacy virtualization and the challenges of self-managing clusters.
- 36:45 — The Future Convergence: How the industry is moving toward a convergence of IaC and orchestration, using new patterns like state graphs to bridge the gap.

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/day-two-devops/episodes/d2do285-the-death-of-iac-has-been-greatly-exaggerated/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/day-two-devops/d2do285-the-death-of-iac-has-been-greatly-exaggerated.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.