Application Projects in ArgoCD
What you'll learn: How to use ArgoCD AppProjects to organize applications into logical groups while enforcing security boundaries and deployment policies.
What Are Application Projects?
Think of AppProjects as departments in a company—each department (project) has its own team, resources, and rules about what they can access and modify. In ArgoCD, an AppProject groups related applications together and defines guardrails: which Git repositories they can sync from, which Kubernetes clusters and namespaces they can deploy to, and what resources they're allowed to manage.
Without AppProjects, all applications belong to the "default" project with minimal restrictions—fine for testing, risky for production.
Why Use AppProjects?
Multi-tenancy: Separate team workloads safely. The backend team's project can only deploy to backend-* namespaces, while the frontend team's project is restricted to frontend-* namespaces.
Security boundaries: Prevent accidental or malicious deployments. A project can block certain resource types (like ClusterRoles) or restrict which Git repos are trusted sources.
Policy enforcement: Set sync windows, require manual approval, or define which clusters are valid targets—all at the project level rather than per-application.
How AppProjects Work
When you create an Application, you specify which project it belongs to. ArgoCD validates every sync operation against that project's rules. If your application tries to deploy a CustomResourceDefinition but the project's clusterResourceWhitelist doesn't allow it, the sync fails.
Key Takeaway: AppProjects let you organize applications into secure, policy-driven groups—controlling source repositories, destination clusters/namespaces, and allowed Kubernetes resource types for true multi-tenant GitOps.