RBAC and Project-Based Access Control
What you'll learn: How to implement fine-grained access control in ArgoCD using RBAC policies and Projects to secure multi-tenant GitOps environments.
Understanding the Security Model
Imagine a shared apartment building where different tenants need access to their own units but shouldn't enter others'. ArgoCD's RBAC (Role-Based Access Control) combined with Projects creates similar boundaries in your Kubernetes deployments.
ArgoCD Projects act as logical groupings that define what resources (clusters, namespaces, Git repos) a set of applications can access. RBAC policies then determine who can perform what actions on those Projects.
How RBAC and Projects Work Together
Projects define the "what":
- Allowed source Git repositories
- Destination clusters and namespaces
- Permitted Kubernetes resource types
- Cluster resource whitelists/blacklists
RBAC defines the "who":
- User or group authentication (local or SSO)
- Permissions per project or application
- Actions: get, create, update, delete, sync, override
Multi-Tenant Access Control
In a multi-tenant environment, you might have:
- Team A can only deploy to
prod-cluster/team-a-*namespaces fromgithub.com/team-a/*repos - Team B has similar boundaries for their resources
- Platform team has full access across all Projects
This prevents teams from accidentally (or intentionally) modifying each other's deployments while sharing the same ArgoCD instance.
SSO Integration
Rather than managing local ArgoCD users, SSO integration (via OIDC, SAML, LDAP) maps external groups to ArgoCD roles. Your existing identity provider becomes the single source of truth for authentication, while ArgoCD handles authorization through RBAC policies.
Key Takeaway: ArgoCD's RBAC and Project-based access control enable secure multi-tenancy by combining Projects (resource boundaries) with RBAC policies (user permissions) and SSO (centralized authentication), ensuring teams can only access their designated environments and applications.