Terraforming ArgoCD: The GitOps Bridge
summary
Uses the Terraform provider for ArgoCD to bridge existing Terraform pipelines and Argo CD so clusters, projects, tokens and applications get provisioned in the same plan/apply. Builds a Terraform module that wraps a common Helm chart, passes AWS resource IDs (security groups, ElastiCache/Redis connection strings, IAM mappings) into Argo CD Application resources, and registers EKS clusters in a hub‑and‑spoke topology. Works for incremental ECS→EKS migrations and developer self‑service, but infra and ArgoCD application resources are not continuously reconciled.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:42GitOps bridge concept
- 1:45Distributed system migration
- 3:12Moving from ECS to Kubernetes
- 4:16Argo CD Terraform provider
- 5:20Hub-spoke platform setup
- 6:21Application deployment with Terraform
- 7:26Live demo: app deployment
- 9:58Trade-offs of GitOps bridge
- 13:30Manual edits in lower envs
- 13:50Conclusion
- 14:10Q&A
related talks
29mTake the Best of Both Worlds Using Terraform and Argo CD
34mInfrastructure at Scale Using ArgoCD
27mArgoCD as the Engine of a Brownfield Migration to Kubernetes
01h 32mUsing Terraform and AWS to create environments on the fly
26mGitOps Me Some of That! Managing Hundreds of Clusters with Argo CD
27mExploring Argo
31mScaling Kubernetes Fleet Management Using GitOps Bridge
27mPlatform Engineering with the Argo Ecosystem: The Elastic Story