Skip to content

Commit

Permalink
Added an example of project scoped cluster (argoproj#16210)
Browse files Browse the repository at this point in the history
Signed-off-by: Christian Hernandez <[email protected]>
Signed-off-by: Kevin Lyda <[email protected]>
  • Loading branch information
christianh814 authored and lyda committed Mar 28, 2024
1 parent d85f0e0 commit ef651f9
Showing 1 changed file with 22 additions and 0 deletions.
22 changes: 22 additions & 0 deletions docs/user-guide/projects.md
Original file line number Diff line number Diff line change
Expand Up @@ -321,6 +321,28 @@ stringData:

All the examples above talk about Git repositories, but the same principles apply to clusters as well.

```yaml
apiVersion: v1
kind: Secret
metadata:
name: mycluster-secret
labels:
argocd.argoproj.io/secret-type: cluster
type: Opaque
stringData:
name: mycluster.com
project: my-project1 # Project scoped
server: https://mycluster.com
config: |
{
"bearerToken": "<authentication token>",
"tlsClientConfig": {
"insecure": false,
"caData": "<base64 encoded certificate>"
}
}
```

With project-scoped clusters we can also restrict projects to only allow applications whose destinations belong to the
same project. The default behavior allows for applications to be installed onto clusters which are not a part of the same
project, as the example below demonstrates:
Expand Down

0 comments on commit ef651f9

Please sign in to comment.