Limited Time Offer!

For Less Than the Cost of a Starbucks Coffee, Access All DevOpsSchool Videos on YouTube Unlimitedly.
Master DevOps, SRE, DevSecOps Skills!

Enroll Now

SOURCE REPOSITORIES vs SCOPED REPOSITORIES in ArgoCD

Projects SOURCE REPOSITORIES

Git respositories where application manifests are permitted to be retrieved from.
Restrict what may be deployed (trusted Git source repositories). Normally, an ArgoCD admin creates a project and decides in advance which clusters and Git repositories it defines.

Project scoped Repositories

Git respositories where application manifests are permitted to be retrieved from.
But Normally, an ArgoCD admin creates a project and decides in advance which clusters and Git repositories it defines.

It is possible to offer a self-service process for developers so that they can add a repository and/or cluster in a project on their own even after the initial creation of the project.

Once the appropriate RBAC rules are in place, developers can create their own Git repositories and (assuming they have the correct credentials) can add them in an existing project either from the UI or the CLI. Both the User interface and the CLI have the ability to optionally specify a project.

If a project is specified then the respective cluster/repository is considered project scoped:

Rajesh Kumar
Follow me
Latest posts by Rajesh Kumar (see all)
Subscribe
Notify of
guest
0 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x