Skip to content
This repository was archived by the owner on Jul 10, 2021. It is now read-only.

Update commands.md #2122

Merged
merged 5 commits into from
Mar 3, 2021
Merged

Update commands.md #2122

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
cc18f6d
Update commands.md
snalvi Jan 11, 2021
049574f
Merge branch 'master' into patch-1
snalvi Jan 30, 2021
abf6ced
Merge branch 'master' into patch-1
aimeeu Feb 5, 2021
123401f
Merge branch 'master' into patch-1
emagana Feb 16, 2021
4b0fc80
Merge branch 'master' into patch-1
aimeeu Mar 3, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions reference/halyard/commands.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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.
Expand Down