1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00

gcloud: Wed May 15 09:19:06 UTC 2024

This commit is contained in:
Automated 2024-05-15 09:19:06 +00:00
parent e8259d86b1
commit 3b84182be4
193 changed files with 10091 additions and 581 deletions

View file

@ -5,7 +5,9 @@ NAME
SYNOPSIS
gcloud compute sole-tenancy node-groups create NAME
--node-template=NODE_TEMPLATE --target-size=TARGET_SIZE
[--description=DESCRIPTION] [--maintenance-policy=MAINTENANCE_POLICY]
[--description=DESCRIPTION]
[--maintenance-interval=MAINTENANCE_INTERVAL]
[--maintenance-policy=MAINTENANCE_POLICY]
[--maintenance-window-start-time=START_TIME] [--zone=ZONE]
[--autoscaler-mode=AUTOSCALER_MODE
: --max-nodes=MAX_NODES --min-nodes=MIN_NODES]
@ -36,6 +38,20 @@ OPTIONAL FLAGS
--description=DESCRIPTION
An optional description of this resource.
--maintenance-interval=MAINTENANCE_INTERVAL
Specifies the frequency of planned maintenance events.
MAINTENANCE_INTERVAL must be one of:
as-needed
hosts are eligible to receive infrastructure and hypervisor updates
as they become available.
recurrent
hosts receive planned infrastructure and hypervisor updates on a
periodic basis, but not more frequently than every 28 days. This
minimizes the number of planned maintenance operations on
individual hosts and reduces the frequency of disruptions, both
live migrations and terminations, on individual VMs.
--maintenance-policy=MAINTENANCE_POLICY
Determines the maintenance behavior during host maintenance events. For
more information, see

View file

@ -37,6 +37,9 @@ COMMANDS
list-nodes
List Compute Engine sole-tenant nodes present in a nodegroup.
perform-maintenance
Perform maintenance on nodes in a Compute Engine node group.
remove-iam-policy-binding
Remove IAM policy binding from a Compute Engine node group.

View file

@ -0,0 +1,68 @@
NAME
gcloud compute sole-tenancy node-groups perform-maintenance - perform
maintenance on nodes in a Compute Engine node group
SYNOPSIS
gcloud compute sole-tenancy node-groups perform-maintenance NAME
--nodes=NODE,[NODE,...] [--start-time=START_TIME] [--zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Perform maintenance on nodes in a Compute Engine node group.
EXAMPLES
To perform maintenance on nodes in a node group, run:
$ gcloud compute sole-tenancy node-groups perform-maintenance \
my-node-group --nodes=node-1,node-2 \
--start-time=2023-05-01T00:00:00.000-08:00
POSITIONAL ARGUMENTS
NAME
Name of the node group to operate on.
REQUIRED FLAGS
--nodes=NODE,[NODE,...]
The names of the nodes to perform maintenance on.
OPTIONAL FLAGS
--start-time=START_TIME
The requested time for the maintenance window to start. The timestamp
must be an RFC3339 valid string.
--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.
GCLOUD WIDE FLAGS
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.
NOTES
These variants are also available:
$ gcloud alpha compute sole-tenancy node-groups perform-maintenance
$ gcloud beta compute sole-tenancy node-groups perform-maintenance