From ef651f9c3c49af3e7bc5649f874b4b39b25de000 Mon Sep 17 00:00:00 2001 From: Christian Hernandez Date: Wed, 1 Nov 2023 17:46:02 -0700 Subject: [PATCH] Added an example of project scoped cluster (#16210) Signed-off-by: Christian Hernandez Signed-off-by: Kevin Lyda --- docs/user-guide/projects.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/docs/user-guide/projects.md b/docs/user-guide/projects.md index 6fb59b1ef3456..9876405febdeb 100644 --- a/docs/user-guide/projects.md +++ b/docs/user-guide/projects.md @@ -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": "", + "tlsClientConfig": { + "insecure": false, + "caData": "" + } + } +``` + 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: