gcloud compute instance-groups managed update-instances - immediately update selected instances in a Compute Engine managed instance group

gcloud compute instance-groups managed update-instancesNAME(--all-instances    |--instances=INSTANCE,[INSTANCE,…])[--minimal-action=MINIMAL_ACTION; default="none"][--most-disruptive-allowed-action=MOST_DISRUPTIVE_ALLOWED_ACTION; default="replace"][--region=REGION    |--zone=ZONE][GCLOUD_WIDE_FLAG …]

gcloud compute instance-groups managed update-instances allows youto specify the least and the most disruptive actions that can be performed whileupdating the instances. This way you can reduce the risk of rolling out too manychanges at once. Possible actions are:none,refresh,restart andreplace. The level of disruption to theinstance is ordered as:none <refresh <restart <replace.

The command returns the operation status per instance, which might beFAIL,SUCCESS, orMEMBER_NOT_FOUND.MEMBER_NOT_FOUND is returned only forregional groups when the gcloud command-line tool wasn't able to resolve thezone from the instance name.

NAME

Name of the managed instance group to operate on.

Exactly one of these must be specified:

--all-instances

Update all instances in the group.

--instances=INSTANCE,[INSTANCE,…]

Names of instances to update.

--minimal-action=MINIMAL_ACTION; default="none"

Use this flag to minimize disruption as much as possible or to apply a moredisruptive action than is strictly necessary. The MIG performs at least thisaction on each instance while updating. If the update requires a more disruptiveaction than the one specified here, then the more disruptive action isperformed. If you omit this flag, the update uses theminimal-action value from the MIG's updatepolicy, unless it is not set in which case the default isreplace.

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 machinetype.

replace

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 you canafford. At most, the MIG performs the specified action on each instance whileupdating. If the update requires a more disruptive action than the one specifiedhere, then the update fails and no changes are made. If you omit this flag, theupdate uses themost-disruptive-allowed-action value fromthe MIG's update policy, unless it is not set in which case the default isreplace.

MOST_DISRUPTIVE_ALLOWED_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 machinetype.

replace

Replace old VMs according to the --replacement-method flag.

At most one of these can be specified:

--region=REGION

Region of the managed instance group to operate on. If not specified, you mightbe prompted to select a region (interactive mode only).

A list of regions can be fetched by running:

gcloudcomputeregionslist

Overrides the defaultcompute/region property value for thiscommand invocation.

--zone=ZONE

Zone of the managed instance group to operate on. If not specified, you might beprompted to select a zone (interactive mode only).

A list of zones can be fetched by running:

gcloudcomputezoneslist

Overrides the defaultcompute/zone property value for this commandinvocation.

Run$gcloud help for details.