Taming the Chaos: Fine-Grained RBAC in Argo CD for Incident Avoidance
summary
Intuit extends Argo CD RBAC to allow action-level permissions (action suffixed by resource path) so UI users can delete pods only while being denied deletes of ReplicaSets, Rollouts or the application; platform runs 50+ instances and manages 31,000 applications and reports 8x developer productivity. Policy integrates with Dex SSO and a three-tier role model (dev, devops, admin), keeps backward-compatible global rules, and blocks the accidental deletes that caused ~20% of risky UI deletions.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:44Developer productivity challenges
- 3:31Argo CD UI common actions
- 5:18Why developers delete resources
- 7:46Risks in Argo CD UI
- 9:14Safer operations goals
- 9:57Policy syntax limitations
- 11:22Fine-grained RBAC feature
- 13:10Intuit's RBAC structure
- 15:18RBAC configuration at Intuit
- 17:27User experience after RBAC
- 18:08Key takeaways
- 19:12Q&A
related talks
25mArgo CD Ephemeral Access in Action: Lessons Learned While Runnin...
24mThe Hidden Dangers of Defaults: Securing Multi-Tenant Argo CD Install...
31mAttacking Argo CD with Argo CD (and then Defending)
24mManaging Argo CD Multi-Tenancy Effectively
13mMitigating Privilege Escalation in Multi-Tenant Argo CD
26mUnlocking the Power of Multi-Tenancy in ArgoCD: A Journey with Expedia..
28mArgo CD Maintainer's Panel
17mRedefining the Multi-Cluster Story of Argo CD