How and When to Flux your Terraform
summary
Demo shows a k3d cluster with Flux and a terraform-controller CRD that runs terraform inside Kubernetes, using a Git repo for modules and a terraform Runner that outputs plan and state as Kubernetes objects. Cloud API tokens flow from K8s Secrets into terraform variables and terraform outputs are written back to Secrets; readable plans go to plan-in-configmap, state-in-secret or an external backend. A manual approval toggle stops automatic apply. One rollout reports ~20 resources provisioned across two teams in three months.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:49Speakers and topic
- 2:31Terraform Controller intro
- 3:34Live demo: cloud VM
- 9:38Controller workflows
- 14:20When to use Controller
- 16:52Demo: app dependencies
- 22:38Key takeaways
- 23:43Q&A
related talks
27mHow to Achieve (Actual) GitOps with Terraform and Flux
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
39mEnhance Your Kubernetes Experience with GitOps & Flux
15mTerraform, GitOps & Kubernetes: manage infrastructure & aas
26mFlux: Multi-tenancy Deep Dive
27mOrchestrating Multi-Tenancy Kubernetes Environments with Flux