imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-09 10:56:49 +00:00
Code Activity

gcloud: Wed Feb 8 10:13:59 UTC 2023

Browse source
This commit is contained in:
Automated 2023-02-08 10:13:59 +00:00
parent fc11b54760
commit 11068cb123
240 changed files with 8982 additions and 619 deletions
Download patch file Download diff file Expand all files Collapse all files

10
gcloud/beta/compute/instance-groups/managed/set-autoscaling
View file

@ -238,8 +238,14 @@ FLAGS
autoscaler scales the group to have at least as many VMs as defined by
the minimum required instances. After the configured duration, if there
is no need to maintain capacity, the autoscaler starts removing
instances after a 10-minute stabilization period and (if configured)
following scale-in controls.
instances after the usual stabilization period and after scale-in
controls (if configured). For more information, see Delays in scaling
in
(https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#delays_in_scaling_in)
and Scale-in controls
(https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#scale-in_controls).
This ensures you don't accidentally lose capacity immediately after the
scaling schedule ends.
--schedule-min-required-replicas=MIN_REQUIRED_REPLICAS
How many VMs the autoscaler should provision for the duration of this

9
gcloud/beta/compute/instance-groups/managed/set-instance-template
View file

@ -22,6 +22,15 @@ DESCRIPTION
▪ Use the rolling-action start-update command.
▪ Use the API to set the group's updatePolicy.type to PROACTIVE.
EXAMPLES
Running:
gcloud beta compute instance-groups managed set-instance-template \
example-managed-instance-group --template=example-global-instance-template
Sets the group's instance template to a global instance template resource:
'example-global-instance-template'.
POSITIONAL ARGUMENTS
NAME
Name of the managed instance group to operate on.

33
gcloud/beta/compute/instance-groups/managed/update-autoscaling
View file

@ -137,10 +137,14 @@ FLAGS
scaling schedule that is currently active the disabled scaling
schedule stops being effective immediately after it moves into
DISABLED state. If there is no need to maintain capacity, the
autoscaler starts removing instances after a 10-minute stabilization
period and (if configured) following scale-in controls. This ensures
you don't accidentally lose capacity immediately after the scaling
schedule ends.
autoscaler starts removing instances after the usual stabilization
period and after scale-in controls (if configured). For more
information, see Delays in scaling in
(https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#delays_in_scaling_in)
and Scale-in controls
(https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#scale-in_controls).
This ensures you don't accidentally lose capacity immediately after
the scaling schedule ends.
--enable-schedule=SCHEDULE_NAME
Name of the scaling schedule to be enabled.
@ -157,9 +161,14 @@ FLAGS
scaling schedule that is currently active, the deleted scaling
schedule stops being effective immediately after it is deleted. If
there is no need to maintain capacity, the autoscaler starts removing
instances after a 10-minute stabilization period and (if configured)
following scale-in controls. This ensures you don't accidentally lose
capacity immediately after the scaling schedule ends.
instances after the usual stabilization period and after scale-in
controls (if configured). For more information, see Delays in scaling
in
(https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#delays_in_scaling_in)
and Scale-in controls
(https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#scale-in_controls).
This ensures you don't accidentally lose capacity immediately after
the scaling schedule ends.
--set-schedule=SCHEDULE_NAME
A unique name for the scaling schedule to be configured.
@ -212,8 +221,14 @@ FLAGS
autoscaler scales the group to have at least as many VMs as defined by
the minimum required instances. After the configured duration, if there
is no need to maintain capacity, the autoscaler starts removing
instances after a 10-minute stabilization period and (if configured)
following scale-in controls.
instances after the usual stabilization period and after scale-in
controls (if configured). For more information, see Delays in scaling
in
(https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#delays_in_scaling_in)
and Scale-in controls
(https://cloud.google.com/compute/docs/autoscaler/understanding-autoscaler-decisions#scale-in_controls).
This ensures you don't accidentally lose capacity immediately after the
scaling schedule ends.
--schedule-min-required-replicas=MIN_REQUIRED_REPLICAS
How many VMs the autoscaler should provision for the duration of this