docs: document more cluster fields (argoproj#11491)

* docs: document more cluster fields Signed-off-by: Michael Crenshaw <[email protected]> * Update docs/operator-manual/declarative-setup.md Co-authored-by: Nicholas Morey <[email protected]> Signed-off-by: Michael Crenshaw <[email protected]> * Update docs/operator-manual/declarative-setup.md Co-authored-by: asingh <[email protected]> Signed-off-by: Michael Crenshaw <[email protected]> * remove shard field I don't think the shard field actually does anything. --------- Signed-off-by: Michael Crenshaw <[email protected]> Co-authored-by: Nicholas Morey <[email protected]> Co-authored-by: asingh <[email protected]>
tkasuz · Mar 16, 2023 · 481ee54 · 481ee54
1 parent 93c87c0
commit 481ee54
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/docs/operator-manual/declarative-setup.md b/docs/operator-manual/declarative-setup.md
@@ -515,6 +515,7 @@ The secret data must include following fields:
 * `server` - cluster api server url
 * `namespaces` - optional comma-separated list of namespaces which are accessible in that cluster. Cluster level resources would be ignored if namespace list is not empty.
 * `clusterResources` - optional boolean string (`"true"` or `"false"`) determining whether Argo CD can manage cluster-level resources on this cluster. This setting is used only if the list of managed namespaces is not empty.
+* `project` - optional string to designate this as a project-scoped cluster.
 * `config` - JSON representation of following data structure:
 
 ```yaml