Talk Deep Dive
summary
Argues that Terraform handles imports and idempotency so it’s the practical choice for stateful infra, and shows patterns to manage Helm charts via Terraform + GitLab CI (Jenkins is an alternative) while acknowledging Flux introduces a second reconciler. Demonstrates the real failure mode: out‑of‑band changes that break reconciliation, quantifies risk through operational anecdotes, and recommends lock down out‑of‑band changes early with policy enforcement to make the pipeline reliable.
AI-written summary · about
related talks
35mMisadventures with Terraform
32mManaging Terraform resource drift using the GitOps method
30mTerraform in Depth QA and Fireside Chat
27mOptimizing Terraform integration inside GitLab CI/CD pipelines
27mHow to Achieve (Actual) GitOps with Terraform and Flux
15mTerraform, GitOps & Kubernetes: manage infrastructure & aas
01h 00mGotchas using Terraform in a secure delivery pipeline
30mHow and When to Flux your Terraform