Project Restrictions and Whitelists
What you'll learn: How to define security boundaries in ArgoCD Projects by controlling which destinations, source repositories, and cluster resources applications can use.
The Security Gatekeeper
Think of ArgoCD Projects as security checkpoints at an airport. Just as travelers are screened and only allowed to board specific flights to approved destinations, applications within a project can only deploy to whitelisted clusters, pull from approved Git repos, and manage permitted Kubernetes resources.
Core Restriction Types
ArgoCD Projects enforce three critical boundaries:
Destination Whitelists
Control where applications can deploy. You specify allowed cluster URLs and namespaces. An application in a "dev-team" project might only deploy to dev-cluster in the dev-* namespaces, preventing accidental production deployments.
Source Repository Whitelists
Control what code can be deployed. You define allowed Git repository URLs (with wildcards supported). This prevents teams from deploying manifests from unauthorized or external repos.
Cluster Resource Whitelists/Blacklists
Control what resources applications can manage. You can whitelist specific Kubernetes resource types (like Deployment, Service) and blacklist dangerous ones (like ClusterRole). This prevents privilege escalation and restricts cluster-wide changes.
Why This Matters
Without restrictions, any application could deploy anything, anywhere—a security nightmare in multi-tenant clusters. Project restrictions enforce the principle of least privilege: teams get exactly the permissions they need, nothing more.
When combined with RBAC, projects become powerful isolation boundaries that let you safely share ArgoCD across multiple teams while preventing cross-contamination of environments and unauthorized resource access.
Key Takeaway: Project restrictions act as declarative security policies that whitelist allowed destinations, source repos, and resource types, ensuring applications can only deploy approved code to approved places with approved permissions.