Building a Bridge Between Argo CD and Terraform
summary
Presents a concrete GitOps-Bridge design pattern that moves Helm installs out of Terraform and into Argo CD, with Terraform remaining the source of truth for cloud metadata (IAM roles, static IPs, SQS URLs). Implements that metadata as cluster secret labels/annotations (or cluster configuration) and bootstraps Argo CD (in-cluster or external) via the Terraform ArgoCD provider. Uses ApplicationSet and the ApplicationSet cluster generator to select addons and layered values files; demo deploys ~13 addons and generates ~30–50 applications successfully.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 2:07Combining Terraform with Argo CD
- 7:28In-cluster Argo CD setup with Terraform
- 13:11External Argo CD with Terraform
- 22:27Summary and call to action
- 24:37Q&A
related talks
01h 32mUsing Terraform and AWS to create environments on the fly
29mBridge the Gap Between Terraform and GitOps
02h 47mA GitOps Architecture from Scratch: Gitlab, Ansible, Terraform, Kub and AWS
30mBuild and manage complex application platforms with Terraform
44mTaming the cloud sprawl
26mDo NOT click-ops your data infrastructure
35mMulti Region Terraform Deployments
27mCase Study: Re-Thinking Our Infrastructure Tooling