gcloud alpha compute sole-tenancy node-groups simulate-maintenance-event - simulate maintenance of a Compute Engine node group
gcloud alpha compute sole-tenancy node-groups simulate-maintenance-event NAME [--async] [--nodes=[NODE,...]] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...]
(ALPHA) Simulate maintenance of a Compute Engine node group.
To simulate maintenance of a node group, run:
$ gcloud alpha compute sole-tenancy node-groups \ simulate-maintenance-event my-node-group --nodes=example-nodes
- NAME
Name of the node group to operate on.
- --async
Return immediately, without waiting for the operation in progress to complete.
- --nodes=[NODE,...]
The names of the nodes to simulate maintenance event.
- --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.
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 alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. This variant is also available:
$ gcloud beta compute sole-tenancy node-groups \ simulate-maintenance-event