From cc18f6dbecea0194c3a440d042e3708dd04b634b Mon Sep 17 00:00:00 2001 From: Saman Alvi Date: Sun, 10 Jan 2021 19:13:57 -0500 Subject: [PATCH] Update commands.md Updating description for `--only-spinnaker-managed` --- reference/halyard/commands.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/reference/halyard/commands.md b/reference/halyard/commands.md index 9f23601520..b9a50a1cc5 100644 --- a/reference/halyard/commands.md +++ b/reference/halyard/commands.md @@ -9611,7 +9611,7 @@ This can only be set when --kinds is empty or not set. * `--omit-namespaces`: (*Default*: `[]`) A list of namespaces this Spinnaker account cannot deploy to or cache. This can only be set when --namespaces is empty or not set. * `--only-spinnaker-managed`: (*Default*: `false`) (V2 Only) When true, Spinnaker will only cache/display applications that have been -created by Spinnaker; as opposed to attempting to configure applications for resources already present in Kubernetes. +created by Spinnaker; as opposed to attempting to configure applications for resources already present in Kubernetes. Resources already present in Kubernetes will need to be annotated manually with the Spinnaker [application moniker](https://spinnaker.io/reference/providers/kubernetes-v2/#moniker) if set to true. * `--provider-version`: (*Default*: `v2`) There are currently two versions of the Kubernetes Provider: V1 and V2. This allows you to pick the version of the provider (not the resources it manages) to run within Spinnaker.V1 is scheduled for removal in Spinnaker 1.21; we recommend using V2 only. * `--read-permissions`: (*Default*: `[]`) A user must have at least one of these roles in order to view this account's cloud resources. * `--required-group-membership`: (*Default*: `[]`) A user must be a member of at least one specified group in order to make changes to this account's cloud resources. @@ -9681,7 +9681,7 @@ This can only be set when --kinds is empty or not set. * `--omit-namespaces`: (*Default*: `[]`) A list of namespaces this Spinnaker account cannot deploy to or cache. This can only be set when --namespaces is empty or not set. * `--only-spinnaker-managed`: (V2 Only) When true, Spinnaker will only cache/display applications that have been -created by Spinnaker; as opposed to attempting to configure applications for resources already present in Kubernetes. +created by Spinnaker; as opposed to attempting to configure applications for resources already present in Kubernetes. Resources already present in Kubernetes will need to be annotated manually with the Spinnaker [application moniker](https://spinnaker.io/reference/providers/kubernetes-v2/#moniker) if set to true. * `--provider-version`: There are currently two versions of the Kubernetes Provider: V1 and V2. This allows you to pick the version of the provider (not the resources it manages) to run within Spinnaker.V1 is scheduled for removal in Spinnaker 1.21; we recommend using V2 only. * `--read-permissions`: A user must have at least one of these roles in order to view this account's cloud resources. * `--remove-custom-resource`: Remove this Kubernetes custom resource by name from the list of custom resources to manage.