ArgoCD RBAC and User Management
You'll learn how to control who can do what in ArgoCD by configuring role-based access control to limit permissions across teams and users.
What Is RBAC in ArgoCD?
Think of ArgoCD RBAC like a hotel key card system: some guests can only access their rooms, while managers can open any door, and cleaning staff have specific access patterns. Similarly, ArgoCD lets you define roles (what actions are allowed) and assign them to users or groups (who gets those permissions).
By default, ArgoCD gives admin users full control, but in production environments with multiple teams, you need granular control: developers might deploy to dev environments, while only ops teams can touch production.
How RBAC Works
ArgoCD RBAC is configured in the argocd-rbac-cm ConfigMap. You define:
- Policies: Rules that grant or deny specific actions (like
get,sync,delete) on resources (applications, projects, repositories) - Groups/Users: Map authentication identities to roles
Policy syntax follows this pattern:
p, <subject>, <resource>, <action>, <object>, <effect>
For example, to let the "developers" group sync applications in the "dev-project":
p, role:developers, applications, sync, dev-project/*, allow
Key Components
- Built-in roles:
role:admin(full access) androle:readonly(view-only) - Custom roles: Define your own with specific permissions
- SSO integration: Connect with LDAP, OIDC, or SAML to map organizational groups
RBAC prevents accidental deletions, enforces separation of duties, and maintains audit trails of who performed which actions.
Key Takeaway:
ArgoCD RBAC restricts user permissions through policy-based rules in the argocd-rbac-cm ConfigMap, enabling secure multi-tenant GitOps workflows with appropriate access boundaries.