Unlocking the Power of Multi-Tenancy in ArgoCD: A Journey with Expedia..
summary
Expedia’s platform runs Argo CD across 600+ clusters with 20k nodes, 200k pods and 11k apps and uses Backstage, GitHub, Jenkins/GitHub Actions, Spinnaker and AWS EKS. Multi-tenancy enforces namespace vs cluster-scoped Argo instances, IAM role assumption for least-privilege cluster access, two RBAC layers, and active-active regional Argo instances for resiliency. Policy is via global AppProject enforced inheritance, default project lockdown, appset-for-bootstrap patterns, and a reviewed workflow for any cluster-wide resource requests.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:02Agenda overview
- 3:11Why multi-tenancy matters
- 4:14Multi-tenancy approaches
- 5:40Developer platform workflow
- 7:50Multi-tenant foundation
- 10:37Cluster vs namespace scope
- 11:59RBAC in ArgoCD/Kubernetes
- 13:45Project-level RBAC
- 15:33Projects and security policies
- 17:44Global projects inheritance
- 18:47Default project risks
- 19:28Project management strategy
- 20:10ApplicationSet pattern
- 21:14Multi-tenancy advantages
- 22:18Deployment flexibility
- 23:22Best practices
- 24:49Security and RBAC tuning
- 25:11Q&A
related talks
24mManaging Argo CD Multi-Tenancy Effectively
38mMulti-Tenancy For Argo Workflows And Argo CD At Adobe
21mMulti-Tenant ArgoCD with security and isolation
34mInfrastructure at Scale Using ArgoCD
23mArgo at Scale: Navigating Complex Multi-Dimensional Deployments Across H...
28mThe ArgoCD AppProject - What Is a Project and How to Power Your...
24mScaling Argo Security and Multi-Tenancy in AWS EKS at the New York Times
17mRedefining the Multi-Cluster Story of Argo CD