Bridge the Gap Between Terraform and GitOps
summary
A controller called Terraform Bridge reads Terraform state (S3 backend supported) and maps root-level outputs into Kubernetes objects via three CRDs ClusterBackend, TFState, ClusterTFState. It fetches outputs like RDS address, AZ, and IAM role ARN and applies JSON or merge patches (env vars, annotations, nodeAffinity) to Deployments and ServiceAccounts, supports go-template functions, multiple backends, configurable refresh intervals, and continuous reconciliation. It integrates with existing Terraform workflows and does not replace Terraform Cloud.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:49Kubernetes isn’t only IaC tool
- 4:57Terraform with Kubernetes
- 7:04Developer experience with Terraform
- 8:33Terraform vs GitOps gap
- 9:56TF Bridge project purpose
- 10:38TF Bridge architecture
- 14:17TF Bridge use cases
- 16:04Live demo of TF Bridge
- 25:24Q&A
related talks
25mBuilding a Bridge Between Argo CD and Terraform
32mManaging Terraform resource drift using the GitOps method
30mHow and When to Flux your Terraform
35mMisadventures with Terraform
31mScaling Kubernetes Fleet Management Using GitOps Bridge
17mTerramate the Tool That Scales Your Terraform Code
39mTerraform Practices to Enable Infrastructure Scaling
29mInfinity and beyond: Scaling Terraform for the global enterprise