Multi-Tenancy For Argo Workflows And Argo CD At Adobe
summary
Adobe runs Argo Workflows and Argo CD in a hub‑and‑spoke setup that enforces namespace‑level isolation using Azure AD group annotations on service accounts, Argo Workflows’ namespace RBAC, and Argo CD AppProject scoping to whitelist git repos and target namespaces. The operator runs with a read‑only cluster role plus per‑namespace rolebindings, secrets kept out via Vault, builds use Kaniko builds or off‑cluster CodeBuild for privileged cases, images are mirrored, executor resources increased, and clients get updates through Helm semantic versions — a working, scalable CI/CD multi‑tenant stack.
AI-written summary · about
chapters (16)
- 0:00Multi-tenancy at Adobe
- 2:00Internal dev platform
- 3:43GitOps and Argo CD basics
- 5:06Argo Workflows architecture
- 6:11CI/CD with Argo tools
- 8:40Why multi-tenancy matters
- 10:03Securing Argo Workflows UI
- 13:28Access control in Argo CD UI
- 16:20Isolating client workflows
- 18:30Isolating Argo CD deployments
- 20:15Securing Argo CD operator
- 23:47Client repo management
- 26:54Scaling Argo Workflows
- 28:39Scaling Argo CD
- 30:28Recap and benefits
- 31:11Q&A
related talks
26mUnlocking the Power of Multi-Tenancy in ArgoCD: A Journey with Expedia..
24mManaging Argo CD Multi-Tenancy Effectively
21mMulti-Tenant ArgoCD with security and isolation
20mDemystifying Argo Workflows: An Architectural Deep Dive
23mArgo at Scale: Navigating Complex Multi-Dimensional Deployments Across H...
24mScaling Argo Security and Multi-Tenancy in AWS EKS at the New York Times
34mInfrastructure at Scale Using ArgoCD
30mArgo’s Vibrant Ecosystem and Community