gcloud: Wed Jan 25 10:09:52 UTC 2023

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

@@ -17,7 +17,13 @@ SYNOPSIS
         [--zones=ZONE,[ZONE,...]]
         [--health-check=HEALTH_CHECK | --http-health-check=HTTP_HEALTH_CHECK
           | --https-health-check=HTTPS_HEALTH_CHECK]
-        [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...]
+        [--region=REGION | --zone=ZONE]
+        [--update-policy-max-surge=MAX_SURGE
+          --update-policy-max-unavailable=MAX_UNAVAILABLE
+          --update-policy-min-ready=MIN_READY
+          --update-policy-minimal-action=UPDATE_POLICY_MINIMAL_ACTION
+          --update-policy-most-disruptive-action=UPDATE_POLICY_MOST_DISRUPTIVE_ACTION --update-policy-replacement-method=UPDATE_POLICY_REPLACEMENT_METHOD --update-policy-type=UPDATE_TYPE]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) gcloud beta compute instance-groups managed create creates a Compute
@@ -278,6 +284,97 @@ OPTIONAL FLAGS
           Overrides the default compute/zone property value for this command
           invocation.
 
+     Parameters for setting update policy for this managed instance group.
+
+       --update-policy-max-surge=MAX_SURGE
+          Maximum additional number of VMs that can be created during the
+          update process. This can be a fixed number (e.g. 5) or a percentage
+          of size to the managed instance group (e.g. 10%). Defaults to 0 if
+          the managed instance group has stateful configuration, or to the
+          number of zones in which it operates otherwise.
+
+       --update-policy-max-unavailable=MAX_UNAVAILABLE
+          Maximum number of VMs that can be unavailable during the update
+          process. This can be a fixed number (e.g. 5) or a percentage of size
+          to the managed instance group (e.g. 10%). Defaults to the number of
+          zones in which the managed instance group operates.
+
+       --update-policy-min-ready=MIN_READY
+          Minimum time for which a newly created VM should be ready to be
+          considered available. For example 10s for 10 seconds. See $ gcloud
+          topic datetimes for information on duration formats.
+
+       --update-policy-minimal-action=UPDATE_POLICY_MINIMAL_ACTION
+          Use this flag to minimize disruption as much as possible or to apply
+          a more disruptive action than is strictly necessary. The MIG performs
+          at least this action on each VM while updating. If the update
+          requires a more disruptive action than the one specified here, then
+          the more disruptive action is performed. UPDATE_POLICY_MINIMAL_ACTION
+          must be one of:
+
+           none
+              No action
+           refresh
+              Apply the new configuration without stopping VMs, if possible.
+              For example, use ``refresh`` to apply changes that only affect
+              metadata or additional disks.
+           restart
+              Apply the new configuration without replacing VMs, if possible.
+              For example, stopping VMs and starting them again is sufficient
+              to apply changes to machine type.
+           replace
+              Replace old VMs according to the
+              --update-policy-replacement-method flag.
+
+       --update-policy-most-disruptive-action=UPDATE_POLICY_MOST_DISRUPTIVE_ACTION
+          Use this flag to prevent an update if it requires more disruption
+          than you can afford. At most, the MIG performs the specified action
+          on each VM while updating. If the update requires a more disruptive
+          action than the one specified here, then the update fails and no
+          changes are made. UPDATE_POLICY_MOST_DISRUPTIVE_ACTION must be one
+          of:
+
+           none
+              No action
+           refresh
+              Apply the new configuration without stopping VMs, if possible.
+              For example, use ``refresh`` to apply changes that only affect
+              metadata or additional disks.
+           restart
+              Apply the new configuration without replacing VMs, if possible.
+              For example, stopping VMs and starting them again is sufficient
+              to apply changes to machine type.
+           replace
+              Replace old VMs according to the
+              --update-policy-replacement-method flag.
+
+       --update-policy-replacement-method=UPDATE_POLICY_REPLACEMENT_METHOD
+          Type of replacement method. Specifies what action will be taken to
+          update VMs. Defaults to ``recreate`` if the managed instance group
+          has stateful configuration, or to ``substitute`` otherwise.
+          UPDATE_POLICY_REPLACEMENT_METHOD must be one of:
+
+           recreate
+              Recreate VMs and preserve the VM names. The VM IDs and creation
+              timestamps might change.
+           substitute
+              Delete old VMs and create VMs with new names.
+
+       --update-policy-type=UPDATE_TYPE
+          Specifies the type of update process. You can specify either
+          ``proactive`` so that the managed instance group proactively executes
+          actions in order to bring VMs to their target versions or
+          ``opportunistic`` so that no action is proactively executed but the
+          update will be performed as part of other actions. UPDATE_TYPE must
+          be one of:
+
+           opportunistic
+              Do not proactively replace VMs. Create new VMs and delete old
+              ones on resizes of the group and when you target specific VMs to
+              be updated or recreated.
+           proactive
+              Replace VMs proactively.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,

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

@@ -73,15 +73,15 @@ OPTIONAL FLAGS
          none
             No action
          refresh
-            Apply the new configuration without stopping instances, if
-            possible. For example, use refresh to apply changes that only
-            affect metadata or additional disks.
+            Apply the new configuration without stopping VMs, if possible. For
+            example, use ``refresh`` to apply changes that only affect metadata
+            or additional disks.
          restart
-            Apply the new configuration without replacing instances, if
-            possible. For example, stopping instances and starting them again
-            is sufficient to apply changes to machine type.
+            Apply the new configuration without replacing VMs, if possible. For
+            example, stopping VMs and starting them again is sufficient to
+            apply changes to machine type.
          replace
-            Replace old instances according to the --replacement-method flag.
+            Replace old VMs according to the --replacement-method flag.
 
      --stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME],[mode=MODE],[source=SOURCE]
         Disks considered stateful by the instance group. Managed instance

gcloud/beta/compute/instance-groups/managed/instance-configs/delete

@@ -45,15 +45,15 @@ OPTIONAL FLAGS
          none
             No action
          refresh
-            Apply the new configuration without stopping instances, if
-            possible. For example, use refresh to apply changes that only
-            affect metadata or additional disks.
+            Apply the new configuration without stopping VMs, if possible. For
+            example, use ``refresh`` to apply changes that only affect metadata
+            or additional disks.
          restart
-            Apply the new configuration without replacing instances, if
-            possible. For example, stopping instances and starting them again
-            is sufficient to apply changes to machine type.
+            Apply the new configuration without replacing VMs, if possible. For
+            example, stopping VMs and starting them again is sufficient to
+            apply changes to machine type.
          replace
-            Replace old instances according to the --replacement-method flag.
+            Replace old VMs according to the --replacement-method flag.
 
      --update-instance
         Apply the configuration changes immediately to the instance. If you

gcloud/beta/compute/instance-groups/managed/instance-configs/update

@@ -80,15 +80,15 @@ OPTIONAL FLAGS
          none
             No action
          refresh
-            Apply the new configuration without stopping instances, if
-            possible. For example, use refresh to apply changes that only
-            affect metadata or additional disks.
+            Apply the new configuration without stopping VMs, if possible. For
+            example, use ``refresh`` to apply changes that only affect metadata
+            or additional disks.
          restart
-            Apply the new configuration without replacing instances, if
-            possible. For example, stopping instances and starting them again
-            is sufficient to apply changes to machine type.
+            Apply the new configuration without replacing VMs, if possible. For
+            example, stopping VMs and starting them again is sufficient to
+            apply changes to machine type.
          replace
-            Replace old instances according to the --replacement-method flag.
+            Replace old VMs according to the --replacement-method flag.
 
      --remove-stateful-disks=DEVICE_NAME,[DEVICE_NAME,...]
         Remove stateful configuration for the specified disks from the

gcloud/beta/compute/instance-groups/managed/rolling-action/replace

@@ -38,8 +38,8 @@ FLAGS
 
      --replacement-method=REPLACEMENT_METHOD
         Type of replacement method. Specifies what action will be taken to
-        update instances. Defaults to recreate if the managed instance group
-        has stateful configuration, or to substitute otherwise.
+        update instances. Defaults to ``recreate`` if the managed instance
+        group has stateful configuration, or to ``substitute`` otherwise.
         REPLACEMENT_METHOD must be one of:
 
          recreate

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

@@ -38,8 +38,9 @@ COMMONLY USED FLAGS
         Desired update type. TYPE must be one of:
 
          opportunistic
-            Do not proactively replace instances. Create new instances and
-            delete old on resizes of the group.
+            Do not proactively replace VMs. Create new VMs and delete old ones
+            on resizes of the group and when you target specific VMs to be
+            updated or recreated.
          proactive
             Replace instances proactively.
 
@@ -78,15 +79,15 @@ OTHER FLAGS
         MINIMAL_ACTION must be one of:
 
          refresh
-            Apply the new configuration without stopping instances, if
-            possible. For example, use refresh to apply changes that only
-            affect metadata or additional disks.
+            Apply the new configuration without stopping VMs, if possible. For
+            example, use ``refresh`` to apply changes that only affect metadata
+            or additional disks.
          restart
-            Apply the new configuration without replacing instances, if
-            possible. For example, stopping instances and starting them again
-            is sufficient to apply changes to machine type.
+            Apply the new configuration without replacing VMs, if possible. For
+            example, stopping VMs and starting them again is sufficient to
+            apply changes to machine type.
          replace
-            Replace old instances according to the --replacement-method flag.
+            Replace old VMs according to the --replacement-method flag.
 
      --most-disruptive-allowed-action=MOST_DISRUPTIVE_ALLOWED_ACTION
         Use this flag to prevent an update if it requires more disruption than
@@ -100,20 +101,20 @@ OTHER FLAGS
         MOST_DISRUPTIVE_ALLOWED_ACTION must be one of:
 
          refresh
-            Apply the new configuration without stopping instances, if
-            possible. For example, use refresh to apply changes that only
-            affect metadata or additional disks.
+            Apply the new configuration without stopping VMs, if possible. For
+            example, use ``refresh`` to apply changes that only affect metadata
+            or additional disks.
          restart
-            Apply the new configuration without replacing instances, if
-            possible. For example, stopping instances and starting them again
-            is sufficient to apply changes to machine type.
+            Apply the new configuration without replacing VMs, if possible. For
+            example, stopping VMs and starting them again is sufficient to
+            apply changes to machine type.
          replace
-            Replace old instances according to the --replacement-method flag.
+            Replace old VMs according to the --replacement-method flag.
 
      --replacement-method=REPLACEMENT_METHOD
         Type of replacement method. Specifies what action will be taken to
-        update instances. Defaults to recreate if the managed instance group
-        has stateful configuration, or to substitute otherwise.
+        update instances. Defaults to ``recreate`` if the managed instance
+        group has stateful configuration, or to ``substitute`` otherwise.
         REPLACEMENT_METHOD must be one of:
 
          recreate

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

@@ -20,14 +20,27 @@ SYNOPSIS
           | --initial-delay=INITIAL_DELAY --health-check=HEALTH_CHECK
           | --http-health-check=HTTP_HEALTH_CHECK
           | --https-health-check=HTTPS_HEALTH_CHECK]
-        [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...]
+        [--region=REGION | --zone=ZONE]
+        [--update-policy-max-surge=MAX_SURGE
+          --update-policy-max-unavailable=MAX_UNAVAILABLE
+          --update-policy-min-ready=MIN_READY
+          --update-policy-minimal-action=UPDATE_POLICY_MINIMAL_ACTION
+          --update-policy-most-disruptive-action=UPDATE_POLICY_MOST_DISRUPTIVE_ACTION --update-policy-replacement-method=UPDATE_POLICY_REPLACEMENT_METHOD --update-policy-type=UPDATE_TYPE]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     (BETA) Update a Compute Engine managed instance group.
 
     gcloud beta compute instance-groups managed update allows you to specify or
-    modify the stateful policy and autohealing policy for an existing managed
-    instance group.
+    modify the description and group policies for an existing managed instance
+    group, including the group's update policy and optional autohealing and
+    stateful policies
+
+    The group's update policy defines how an updated VM configuration is
+    applied to existing VMs in the group. For more information, see [Applying
+    new configurations]
+    (https://cloud.google.com/compute/docs/instance-groups/updating-migs) to
+    VMs in a MIG.
 
     A stateful policy defines which resources should be preserved across the
     group. When instances in the group are recreated, stateful resources are
@@ -290,6 +303,97 @@ FLAGS
           Overrides the default compute/zone property value for this command
           invocation.
 
+     Parameters for setting update policy for this managed instance group.
+
+       --update-policy-max-surge=MAX_SURGE
+          Maximum additional number of VMs that can be created during the
+          update process. This can be a fixed number (e.g. 5) or a percentage
+          of size to the managed instance group (e.g. 10%). Defaults to 0 if
+          the managed instance group has stateful configuration, or to the
+          number of zones in which it operates otherwise.
+
+       --update-policy-max-unavailable=MAX_UNAVAILABLE
+          Maximum number of VMs that can be unavailable during the update
+          process. This can be a fixed number (e.g. 5) or a percentage of size
+          to the managed instance group (e.g. 10%). Defaults to the number of
+          zones in which the managed instance group operates.
+
+       --update-policy-min-ready=MIN_READY
+          Minimum time for which a newly created VM should be ready to be
+          considered available. For example 10s for 10 seconds. See $ gcloud
+          topic datetimes for information on duration formats.
+
+       --update-policy-minimal-action=UPDATE_POLICY_MINIMAL_ACTION
+          Use this flag to minimize disruption as much as possible or to apply
+          a more disruptive action than is strictly necessary. The MIG performs
+          at least this action on each VM while updating. If the update
+          requires a more disruptive action than the one specified here, then
+          the more disruptive action is performed. UPDATE_POLICY_MINIMAL_ACTION
+          must be one of:
+
+           none
+              No action
+           refresh
+              Apply the new configuration without stopping VMs, if possible.
+              For example, use ``refresh`` to apply changes that only affect
+              metadata or additional disks.
+           restart
+              Apply the new configuration without replacing VMs, if possible.
+              For example, stopping VMs and starting them again is sufficient
+              to apply changes to machine type.
+           replace
+              Replace old VMs according to the
+              --update-policy-replacement-method flag.
+
+       --update-policy-most-disruptive-action=UPDATE_POLICY_MOST_DISRUPTIVE_ACTION
+          Use this flag to prevent an update if it requires more disruption
+          than you can afford. At most, the MIG performs the specified action
+          on each VM while updating. If the update requires a more disruptive
+          action than the one specified here, then the update fails and no
+          changes are made. UPDATE_POLICY_MOST_DISRUPTIVE_ACTION must be one
+          of:
+
+           none
+              No action
+           refresh
+              Apply the new configuration without stopping VMs, if possible.
+              For example, use ``refresh`` to apply changes that only affect
+              metadata or additional disks.
+           restart
+              Apply the new configuration without replacing VMs, if possible.
+              For example, stopping VMs and starting them again is sufficient
+              to apply changes to machine type.
+           replace
+              Replace old VMs according to the
+              --update-policy-replacement-method flag.
+
+       --update-policy-replacement-method=UPDATE_POLICY_REPLACEMENT_METHOD
+          Type of replacement method. Specifies what action will be taken to
+          update VMs. Defaults to ``recreate`` if the managed instance group
+          has stateful configuration, or to ``substitute`` otherwise.
+          UPDATE_POLICY_REPLACEMENT_METHOD must be one of:
+
+           recreate
+              Recreate VMs and preserve the VM names. The VM IDs and creation
+              timestamps might change.
+           substitute
+              Delete old VMs and create VMs with new names.
+
+       --update-policy-type=UPDATE_TYPE
+          Specifies the type of update process. You can specify either
+          ``proactive`` so that the managed instance group proactively executes
+          actions in order to bring VMs to their target versions or
+          ``opportunistic`` so that no action is proactively executed but the
+          update will be performed as part of other actions. UPDATE_TYPE must
+          be one of:
+
+           opportunistic
+              Do not proactively replace VMs. Create new VMs and delete old
+              ones on resizes of the group and when you target specific VMs to
+              be updated or recreated.
+           proactive
+              Replace VMs proactively.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,

gcloud/beta/compute/instance-groups/managed/update-instances

@@ -66,15 +66,15 @@ OPTIONAL FLAGS
          none
             No action
          refresh
-            Apply the new configuration without stopping instances, if
-            possible. For example, use refresh to apply changes that only
-            affect metadata or additional disks.
+            Apply the new configuration without stopping VMs, if possible. For
+            example, use ``refresh`` to apply changes that only affect metadata
+            or additional disks.
          restart
-            Apply the new configuration without replacing instances, if
-            possible. For example, stopping instances and starting them again
-            is sufficient to apply changes to machine type.
+            Apply the new configuration without replacing VMs, if possible. For
+            example, stopping VMs and starting them again is sufficient to
+            apply changes to machine type.
          replace
-            Replace old instances according to the --replacement-method flag.
+            Replace old VMs according to the --replacement-method flag.
 
      --most-disruptive-allowed-action=MOST_DISRUPTIVE_ALLOWED_ACTION; default="replace"
         Use this flag to prevent an update if it requires more disruption than
@@ -90,15 +90,15 @@ OPTIONAL FLAGS
          none
             No action
          refresh
-            Apply the new configuration without stopping instances, if
-            possible. For example, use refresh to apply changes that only
-            affect metadata or additional disks.
+            Apply the new configuration without stopping VMs, if possible. For
+            example, use ``refresh`` to apply changes that only affect metadata
+            or additional disks.
          restart
-            Apply the new configuration without replacing instances, if
-            possible. For example, stopping instances and starting them again
-            is sufficient to apply changes to machine type.
+            Apply the new configuration without replacing VMs, if possible. For
+            example, stopping VMs and starting them again is sufficient to
+            apply changes to machine type.
          replace
-            Replace old instances according to the --replacement-method flag.
+            Replace old VMs according to the --replacement-method flag.
 
      At most one of these can be specified: