gcloud beta compute sole-tenancy node-groups create - create a Compute Engine node group
gcloud beta compute sole-tenancy node-groups create NAME --node-template=NODE_TEMPLATE --target-size=TARGET_SIZE [--description=DESCRIPTION] [--maintenance-policy=MAINTENANCE_POLICY] [--maintenance-window-start-time=START_TIME] [--zone=ZONE] [--autoscaler-mode=AUTOSCALER_MODE : --max-nodes=MAX_NODES --min-nodes=MIN_NODES] [--share-setting=SHARE_SETTING : --share-with=PROJECT,[PROJECT,...]] [GCLOUD_WIDE_FLAG ...]
(BETA) Create a Compute Engine node group.
To create a node group, run:
$ gcloud beta compute sole-tenancy node-groups create \ my-node-group --node-template=example-template --target-size=4
- NAME
Name of the node group to operate on.
- --node-template=NODE_TEMPLATE
The name of the node template resource to be set for this node group.
- --target-size=TARGET_SIZE
The target initial number of nodes in the node group.
- --description=DESCRIPTION
An optional description of this resource.
- --maintenance-policy=MAINTENANCE_POLICY
Determines the maintenance behavior during host maintenance events. For more information, see https://cloud.google.com/compute/docs/nodes#maintenance_policies. MAINTENANCE_POLICY must be one of:
- default
VM instances on the host are live migrated to a new physical server. This is the default setting.
- migrate-within-node-group
VM instances on the host are live migrated to another node within the same node group.
- restart-in-place
VM instances on the host are terminated and then restarted on the same physical server after the maintenance event has completed.
- --maintenance-window-start-time=START_TIME
The time (in GMT) when planned maintenance operations window begins. The possible values are 00:00, 04:00, 08:00, 12:00, 16:00, 20:00.
- --zone=ZONE
Zone of the node group to operate on. If not specified and the compute/zone property isn't set, you might be prompted to select a zone (interactive mode only).
To avoid prompting when this flag is omitted, you can set the compute/zone property:
$ gcloud config set compute/zone ZONE
A list of zones can be fetched by running:
$ gcloud compute zones list
To unset the property, run:
$ gcloud config unset compute/zone
Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE.
- Autoscaling policy for node groups.
- --autoscaler-mode=AUTOSCALER_MODE
Set the mode of an autoscaler for a node group. AUTOSCALER_MODE must be one of:
- off
to turn off autoscaling.
- on
to permit autoscaling to scale in and out.
- only-scale-out
to permit autoscaling to scale only out and not in.
This flag argument must be specified if any of the other arguments in this group are specified.
- --max-nodes=MAX_NODES
The maximum size of the node group. Must be smaller or equal to 100 and larger than or equal to --min-nodes. Must be specified if --autoscaler-mode is not off.
- --min-nodes=MIN_NODES
The minimum size of the node group. Default is 0 and must be an integer value smaller than or equal to --max-nodes.
- Manage the properties of a shared setting
- --share-setting=SHARE_SETTING
Specify if this node group is shared; and if so, the type of sharing: share with specific projects or folders. SHARE_SETTING must be one of: projects, organization, local.
This flag argument must be specified if any of the other arguments in this group are specified.
- --share-with=PROJECT,[PROJECT,...]
A list of specific projects this node group should be shared with.
These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
This command is currently in beta and might change without notice. These variants are also available:
$ gcloud compute sole-tenancy node-groups create
$ gcloud alpha compute sole-tenancy node-groups create