imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-13 08:27:05 +00:00
Code Activity

gcloud: Wed Jan 8 10:03:00 UTC 2025

Browse source
This commit is contained in:
Automated 2025-01-08 10:03:00 +00:00
parent 52290f76fe
commit 5a9f5ff67e
161 changed files with 2678 additions and 414 deletions
Download patch file Download diff file Expand all files Collapse all files

26
gcloud/compute/instance-groups/managed/create
View file

@ -12,11 +12,14 @@ SYNOPSIS
machine-type=MACHINE_TYPE[,machine-type=MACHINE_TYPE...][,rank=RANK]]
[--instance-selection-machine-types=[MACHINE_TYPE,...]]
[--list-managed-instances-results=MODE]
[--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY]
[--standby-policy-mode=STANDBY_POLICY_MODE]
[--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]]
[--stateful-external-ip=[enabled],
[auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]]
[--stateful-internal-ip=[enabled],
[auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]]
[--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE]
[--target-distribution-shape=SHAPE] [--target-pool=[TARGET_POOL,...]]
[--zones=ZONE,[ZONE,...]]
[--health-check=HEALTH_CHECK | --http-health-check=HTTP_HEALTH_CHECK
@ -151,6 +154,23 @@ OPTIONAL FLAGS
Pagination is enabled for the group's listManagedInstances API
method. maxResults and pageToken query parameters are respected.
--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY
Specifies the number of seconds that the MIG should wait before
suspending or stopping a VM. The initial delay gives the initialization
script the time to prepare your VM for a quick scale out.
--standby-policy-mode=STANDBY_POLICY_MODE
Defines how a MIG resumes or starts VMs from a standby pool when the
group scales out. The default mode is manual. STANDBY_POLICY_MODE must
be one of:
manual
MIG does not automatically resume or start VMs in the standby pool
when the group scales out.
scale-out-pool
MIG automatically resumes or starts VMs in the standby pool when
the group scales out, and replenishes the standby pool afterwards.
--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]
Disks considered stateful by the instance group. Managed instance
groups preserve and reattach stateful disks on VM autohealing, update,
@ -241,6 +261,12 @@ OPTIONAL FLAGS
the instance is deleted manually or when the group size is
decreased.
--stopped-size=STOPPED_SIZE
Specifies the target size of stopped VMs in the group.
--suspended-size=SUSPENDED_SIZE
Specifies the target size of suspended VMs in the group.
--target-distribution-shape=SHAPE
Specifies how a regional managed instance group distributes its
instances across zones within the region. The default shape is even.

12
gcloud/compute/instance-groups/managed/help
View file

@ -73,6 +73,9 @@ COMMANDS
resize
Set managed instance group size.
resume-instances
Resume the suspended instances in a managed instance group.
set-autoscaling
Set autoscaling parameters of a managed instance group.
@ -85,9 +88,18 @@ COMMANDS
set-target-pools
Set target pools of managed instance group.
start-instances
Start the stopped instances in a managed instance group.
stop-autoscaling
Stop autoscaling a managed instance group.
stop-instances
Stop instances owned by a managed instance group.
suspend-instances
Suspend instances owned by a managed instance group.
update
Update a Compute Engine managed instance group.

75
gcloud/compute/instance-groups/managed/resume-instances Normal file
View file

@ -0,0 +1,75 @@
NAME
gcloud compute instance-groups managed resume-instances - resume the
suspended instances in a managed instance group
SYNOPSIS
gcloud compute instance-groups managed resume-instances NAME
--instances=INSTANCE,[INSTANCE,...] [--region=REGION | --zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud compute instance-groups managed resume-instances resumes one or more
instances from a managed instance group, thereby increasing the targetSize
and reducing the targetSuspendedSize of the group.
The command returns the operation status per instance, which might be FAIL,
SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for
regional groups when the gcloud command-line tool wasn't able to resolve
the zone from the instance name.
EXAMPLES
To resume an instance from a managed instance group in the us-central1-a
zone, run:
$ gcloud compute instance-groups managed resume-instances \
example-managed-instance-group --zone=us-central1-a \
--instances=example-instance
POSITIONAL ARGUMENTS
NAME
Name of the managed instance group to operate on.
REQUIRED FLAGS
--instances=INSTANCE,[INSTANCE,...]
Names of instances to resume.
OPTIONAL FLAGS
At most one of these can be specified:
--region=REGION
Region of the managed instance group to operate on. If not specified,
you might be prompted to select a region (interactive mode only).
A list of regions can be fetched by running:
$ gcloud compute regions list
Overrides the default compute/region property value for this command
invocation.
--zone=ZONE
Zone of the managed instance group to operate on. If not specified,
you might be prompted to select a zone (interactive mode only).
A list of zones can be fetched by running:
$ gcloud compute zones list
Overrides the default compute/zone property value for this command
invocation.
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 instance-groups managed resume-instances
$ gcloud beta compute instance-groups managed resume-instances

75
gcloud/compute/instance-groups/managed/start-instances Normal file
View file

@ -0,0 +1,75 @@
NAME
gcloud compute instance-groups managed start-instances - start the stopped
instances in a managed instance group
SYNOPSIS
gcloud compute instance-groups managed start-instances NAME
--instances=INSTANCE,[INSTANCE,...] [--region=REGION | --zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud compute instance-groups managed start-instances starts one or more
instances from a managed instance group, thereby increasing the targetSize
and reducing the targetStoppedSize of the group.
The command returns the operation status per instance, which might be FAIL,
SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for
regional groups when the gcloud command-line tool wasn't able to resolve
the zone from the instance name.
EXAMPLES
To start an instance from a managed instance group in the us-central1-a
zone, run:
$ gcloud compute instance-groups managed start-instances \
example-managed-instance-group --zone=us-central1-a \
--instances=example-instance
POSITIONAL ARGUMENTS
NAME
Name of the managed instance group to operate on.
REQUIRED FLAGS
--instances=INSTANCE,[INSTANCE,...]
Names of instances to start.
OPTIONAL FLAGS
At most one of these can be specified:
--region=REGION
Region of the managed instance group to operate on. If not specified,
you might be prompted to select a region (interactive mode only).
A list of regions can be fetched by running:
$ gcloud compute regions list
Overrides the default compute/region property value for this command
invocation.
--zone=ZONE
Zone of the managed instance group to operate on. If not specified,
you might be prompted to select a zone (interactive mode only).
A list of zones can be fetched by running:
$ gcloud compute zones list
Overrides the default compute/zone property value for this command
invocation.
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 instance-groups managed start-instances
$ gcloud beta compute instance-groups managed start-instances

73
gcloud/compute/instance-groups/managed/stop-instances Normal file
View file

@ -0,0 +1,73 @@
NAME
gcloud compute instance-groups managed stop-instances - stop instances
owned by a managed instance group
SYNOPSIS
gcloud compute instance-groups managed stop-instances NAME
--instances=INSTANCE,[INSTANCE,...] [--force]
[--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud compute instance-groups managed stop-instances stops one or more
instances from a managed instance group
EXAMPLES
To stop an instance from a managed instance group in the us-central1-a
zone, run:
$ gcloud compute instance-groups managed stop-instances \
example-managed-instance-group --zone=us-central1-a \
--instances=example-instance
POSITIONAL ARGUMENTS
NAME
Name of the managed instance group to operate on.
REQUIRED FLAGS
--instances=INSTANCE,[INSTANCE,...]
Names of instances to stop.
OPTIONAL FLAGS
--force
Immediately stop the specified instances, skipping the initial delay,
if one is specified in the standby policy.
At most one of these can be specified:
--region=REGION
Region of the managed instance group to operate on. If not specified,
you might be prompted to select a region (interactive mode only).
A list of regions can be fetched by running:
$ gcloud compute regions list
Overrides the default compute/region property value for this command
invocation.
--zone=ZONE
Zone of the managed instance group to operate on. If not specified,
you might be prompted to select a zone (interactive mode only).
A list of zones can be fetched by running:
$ gcloud compute zones list
Overrides the default compute/zone property value for this command
invocation.
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 instance-groups managed stop-instances
$ gcloud beta compute instance-groups managed stop-instances

79
gcloud/compute/instance-groups/managed/suspend-instances Normal file
View file

@ -0,0 +1,79 @@
NAME
gcloud compute instance-groups managed suspend-instances - suspend
instances owned by a managed instance group
SYNOPSIS
gcloud compute instance-groups managed suspend-instances NAME
--instances=INSTANCE,[INSTANCE,...] [--force]
[--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud compute instance-groups managed suspend-instances suspends one or
more instances from a managed instance group, thereby reducing the
targetSize and increasing the targetSuspendedSize of the group.
The command returns the operation status per instance, which might be FAIL,
SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for
regional groups when the gcloud command-line tool wasn't able to resolve
the zone from the instance name.
EXAMPLES
To suspend an instance from a managed instance group in the us-central1-a
zone, run:
$ gcloud compute instance-groups managed suspend-instances \
example-managed-instance-group --zone=us-central1-a \
--instances=example-instance
POSITIONAL ARGUMENTS
NAME
Name of the managed instance group to operate on.
REQUIRED FLAGS
--instances=INSTANCE,[INSTANCE,...]
Names of instances to suspend.
OPTIONAL FLAGS
--force
Immediately suspend the specified instances, skipping the initial
delay, if one is specified in the standby policy.
At most one of these can be specified:
--region=REGION
Region of the managed instance group to operate on. If not specified,
you might be prompted to select a region (interactive mode only).
A list of regions can be fetched by running:
$ gcloud compute regions list
Overrides the default compute/region property value for this command
invocation.
--zone=ZONE
Zone of the managed instance group to operate on. If not specified,
you might be prompted to select a zone (interactive mode only).
A list of zones can be fetched by running:
$ gcloud compute zones list
Overrides the default compute/zone property value for this command
invocation.
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 instance-groups managed suspend-instances
$ gcloud beta compute instance-groups managed suspend-instances

26
gcloud/compute/instance-groups/managed/update
View file

@ -16,11 +16,14 @@ SYNOPSIS
[--remove-stateful-disks=DEVICE_NAME,[DEVICE_NAME,...]]
[--remove-stateful-external-ips=INTERFACE_NAME,[...]]
[--remove-stateful-internal-ips=INTERFACE_NAME,[...]] [--size=SIZE]
[--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY]
[--standby-policy-mode=STANDBY_POLICY_MODE]
[--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]]
[--stateful-external-ip=[enabled],
[auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]]
[--stateful-internal-ip=[enabled],
[auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]]
[--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE]
[--target-distribution-shape=SHAPE]
[--clear-autohealing
| --initial-delay=INITIAL_DELAY --health-check=HEALTH_CHECK
@ -153,6 +156,23 @@ FLAGS
--size=SIZE
Target number of running instances in managed instance group.
--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY
Specifies the number of seconds that the MIG should wait before
suspending or stopping a VM. The initial delay gives the initialization
script the time to prepare your VM for a quick scale out.
--standby-policy-mode=STANDBY_POLICY_MODE
Defines how a MIG resumes or starts VMs from a standby pool when the
group scales out. The default mode is manual. STANDBY_POLICY_MODE must
be one of:
manual
MIG does not automatically resume or start VMs in the standby pool
when the group scales out.
scale-out-pool
MIG automatically resumes or starts VMs in the standby pool when
the group scales out, and replenishes the standby pool afterwards.
--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]
Disks considered stateful by the instance group. Managed instance
groups preserve and reattach stateful disks on VM autohealing, update,
@ -256,6 +276,12 @@ FLAGS
the instance is deleted manually or when the group size is
decreased.
--stopped-size=STOPPED_SIZE
Specifies the target size of stopped VMs in the group.
--suspended-size=SUSPENDED_SIZE
Specifies the target size of suspended VMs in the group.
--target-distribution-shape=SHAPE
Specifies how a regional managed instance group distributes its
instances across zones within the region. The default shape is even.