How to Achieve (Actual) GitOps with Terraform and Flux
summary
Shows how Flux Terraform Controller runs Terraform from Git with manual plan approval or auto applies, stores state in a Kubernetes Secret by default, and supports drift detection wired to Flux notifications by adding Terraform CRDs to the notification controller. Demo bootstraps Flux with the CLI, provisions Vault via a Helm chart, approves a stored plan, flips to auto reconcile, triggers a Slack alert for a deleted secret and then automatically recreates it. Controller scales to 1500 terraform modules in tests.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 1:11GitOps principles
- 2:14Why use GitOps
- 3:56Introduction to Flux
- 8:15Flux architecture
- 11:00Terraform controller overview
- 16:10Terraform demo
- 25:59Drift detection demo
related talks
39mEnhance Your Kubernetes Experience with GitOps & Flux
30mHow and When to Flux your Terraform
27mLevel Up Your Deployments: Automate with Terraform + Flux
27mAutomate with Terraform + Flux + EKS: Level Up Your Deployments
32mManaging Terraform resource drift using the GitOps method
26mFlux: Multi-tenancy Deep Dive
29mAccelerating GitOps Adoption with Flux
26mGitOps Lifecycle Management