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

gcloud/alpha/compute/instance-groups/managed/rolling-action/start-update

@@ -19,6 +19,27 @@ DESCRIPTION
     start-update updates instances in a managed instance group, according to
     the given versions and the given update policy.
 
+    An instance template version can be either a global or regional resource.
+
+EXAMPLES
+    Running:
+
+        gcloud alpha compute instance-groups managed rolling-action start-update example-managed-instance-group \
+        --version='template=example-global-instance-template'
+
+    Sets the group's instance template version to a global instance template
+    resource: 'example-global-instance-template'.
+
+    To use a regional instance template, specify its full URL.
+
+    Running:
+
+        gcloud alpha compute instance-groups managed rolling-action start-update example-managed-instance-group \
+        --version='template=https://www.googleapis.com/compute/alpha/projects/example-project/regions/us-central1/instanceTemplates/example-regional-instance-template'
+
+    Sets the group's instance template version to a regional instance template
+    resource: 'example-regional-instance-template'.
+
 POSITIONAL ARGUMENTS
      NAME
         Name of the managed instance group to operate on.

gcloud/alpha/compute/instance-groups/managed/set-autoscaling

@@ -243,8 +243,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

gcloud/alpha/compute/instance-groups/managed/set-instance-template

@@ -22,13 +22,34 @@ DESCRIPTION
       ▪ Use the rolling-action start-update command.
       ▪ Use the API to set the group's updatePolicy.type to PROACTIVE.
 
+EXAMPLES
+    Running:
+
+        gcloud alpha compute instance-groups managed set-instance-template \
+        example-managed-instance-group --template=example-global-instance-template
+
+    Sets the instance template for the 'example-managed-instance-group' group
+    to a global resource: 'example-global-instance-template'.
+
+    To use a regional instance template, specify its full URL.
+
+    Running:
+
+        gcloud alpha compute instance-groups managed set-instance-template \
+        example-managed-instance-group \
+        --template=https://www.googleapis.com/compute/alpha/projects/example-project/regions/us-central1/instanceTemplates/example-regional-instance-template
+
+    Sets the instance template for the 'example-managed-instance-group' group
+    to a regional resource: 'example-regional-instance-template'.
+
 POSITIONAL ARGUMENTS
      NAME
         Name of the managed instance group to operate on.
 
 REQUIRED FLAGS
      --template=TEMPLATE
-        Compute Engine instance template resource to be used.
+        Specifies the instance template to use when creating new instances. An
+        instance template is either a global or regional resource.
 
 OPTIONAL FLAGS
      At most one of these can be specified:

gcloud/alpha/compute/instance-groups/managed/update-autoscaling

@@ -142,10 +142,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.
@@ -162,9 +166,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.
@@ -217,8 +226,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