gcloud: Thu Jan 19 00:56:33 UTC 2023

gcloud/beta/compute/instance-groups/managed/create

@@ -5,8 +5,8 @@ NAME
 SYNOPSIS
     gcloud beta compute instance-groups managed create NAME --size=SIZE
         --template=TEMPLATE [--base-instance-name=BASE_INSTANCE_NAME]
-        [--description=DESCRIPTION] [--initial-delay=INITIAL_DELAY]
-        [--instance-redistribution-type=TYPE]
+        [--description=DESCRIPTION] [--[no-]force-update-on-repair]
+        [--initial-delay=INITIAL_DELAY] [--instance-redistribution-type=TYPE]
         [--list-managed-instances-results=MODE]
         [--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]]
         [--stateful-external-ip=[enabled],
@@ -52,6 +52,16 @@ OPTIONAL FLAGS
      --description=DESCRIPTION
         An optional description for this group.
 
+     --[no-]force-update-on-repair
+        Specifies whether to apply the group's latest configuration when
+        repairing a VM. If you updated the group's instance template or
+        per-instance configurations after the VM was created, then these
+        changes are applied when VM is repaired. If this flag is disabled with
+        -no-force-update-on-repair, then updates are applied in accordance with
+        the group's update policy type. By default, this flag is disabled. Use
+        --force-update-on-repair to enable and --no-force-update-on-repair to
+        disable.
+
      --initial-delay=INITIAL_DELAY
         Specifies the length of time during which the instance is known to be
         initializing and should not be autohealed even if unhealthy. This value
@@ -190,6 +200,13 @@ OPTIONAL FLAGS
             requested number of VMs within present resource constraints and to
             maximize utilization of unused zonal reservations. Recommended for
             batch workloads that do not require high availability.
+         any-single-zone
+            The group schedules all instances within a single zone. The zone is
+            chosen based on hardware support, current resources availability,
+            and matching reservations. The group might not be able to create
+            the requested number of VMs in case of zonal resource availability
+            constraints. Recommended for workloads requiring extensive
+            communication between VMs.
          balanced
             The group prioritizes acquisition of resources, scheduling VMs in
             zones where resources are available while distributing VMs as