Argo CD projects, not to be confused with {OCP} projects, provide a way to group applications together. With Argo CD projects, you can specify restrictions on Applications, such as what resources can be deployed and where they can be deployed.
Additionally, you can define Argo CD role-based access control (RBAC) rules at the project level. This approach allows more granular permissions compared to the global settings in the Argo CD custom resource (CR).
While you can define tenant RBAC globally in the Operator’s Argo CD CR, you should define tenant RBAC along with restrictions in the AppProject CR.
If you have a large number of tenants, attempting to manage all tenants with global RBAC might lead to much repetition.
If you have many instances of tenants, some of the project configurations might be common across tenant projects. To reduce duplication and minimize maintenance, use global projects for common configuration and inherit them in tenant projects.
|
Note
|
Always define your projects and never use the default project created with an Argo CD installation by the Operator. |