Meta tags:

Headings (most frequently used words):

update, gcloud, rest, console, for, rolling, permissions, required, this, task, updates, canary, an, instance, group, in, and, on, your, start, additional, examples, roll, control, the, restart, or, replace, regional, managed, maximum, action, whether, is, automatically, apply, vm, configuration, mig, stay, organized, with, collections, save, categorize, content, based, preferences, before, you, begin, limitations, basic, configure, options, monitor, back, stop, speed, of, disruption, level, during, perform, preserve, names, what, next, type, surge, unavailable, minimum, wait, time, minimal, most, disruptive, allowed, replacement, method, forward, status, current, actions, instances, differences, between, updating, versus, zonal, migs, use, fixed, number, percentage, requests, products, pricing, support, resources, engage, verify, rollout, complete, check, stable,

Text of the page (most frequently used words):
the (629), instance (221), for (193), #update (187), and (177), you (176), #instances (170), vms (129), create (127), mig (122), with (100), compute (94), template (91), set (79), that (74), use (71), about (67), zone (67), can (65), troubleshoot (62), group (58), region (57), action (56), new (54), rolling (53), using (53), your (52), example (49), groups (48), disk (47), cloud (46), manage (46), google (45), number (45), view (44), managed (43), regional (43), gcloud (42), following (41), engine (41), configuration (40), all (39), are (39), disks (39), server (39), restart (38), configure (38), replace (37), canary (36), request (36), updates (35), apply (35), this (34), version (34), from (34), target (33), start (33), windows (33), zones (32), overview (32), more (31), instance_group_name (30), performance (30), migs (29), zonal (29), time (29), default (28), specify (27), when (27), monitor (27), reservation (27), status (26), options (26), method (26), want (26), machine (26), being (25), running (22), field (22), have (22), type (22), command (22), disruptive (22), image (21), size (21), current (21), name (21), network (21), hyperdisk (21), sql (21), see (20), updated (20), value (20), updater (20), than (20), only (20), projects (20), perform (20), console (20), access (20), images (20), resources (19), percentage (19), select (19), patch (19), names (19), metadata (19), one (18), resource (18), gpu (18), maxunavailable (17), maxsurge (17), list (17), click (17), change (17), back (17), stateful (17), creation (17), linux (17), policies (16), based (16), not (16), must (16), unavailable (16), option (16), control (16), reservations (16), across (15), then (15), which (15), application (15), rest (15), https (15), com (15), best (15), disruption (15), existing (15), workload (15), virtual (15), snapshots (15), ssh (15), recommendations (15), but (14), additional (14), after (14), instancegroupmanagers (14), global (14), googleapis (14), cli (14), minimal (14), during (14), created (14), host (14), load (14), custom (14), connect (14), how (13), choose (13), availability (13), make (13), versions (13), call (13), roll (13), health (13), persistent (13), permissions (13), delete (13), add (13), service (13), management (13), bulk (13), microsoft (13), cluster (13), details (12), fixed (12), regions (12), new_template (12), wait (12), automatically (12), stop (12), check (12), machines (12), storage (12), sole (12), each (11), get (11), has (11), proactive (11), instancetemplate (11), instancetemplates (11), replacement (11), available (11), run (11), boot (11), testing (11), attached (11), practices (11), workloads (11), other (10), page (10), same (10), values (10), multiple (10), updatepolicy (10), max (10), changes (10), actions (10), allowed (10), api (10), specific (10), project (10), install (10), migrate (10), logs (10), information (9), need (9), healthy (9), templates (9), either (9), out (9), two (9), might (9), recreate (9), project_id (9), flag (9), also (9), 100 (9), these (9), opportunistic (9), test (9), automated (9), central1 (9), process (9), pools (9), currentaction (9), licenses (9), tenant (9), openshift (9), shutdown (9), hpc (9), samples (8), support (8), down (8), its (8), license (8), requests (8), their (8), possible (8), operation (8), been (8), don (8), modify (8), startup (8), requires (8), properties (8), most (8), necessary (8), before (8), enable (8), mode (8), task (8), required (8), provide (8), remove (8), applications (8), manually (8), addresses (8), authentication (8), import (8), cpu (8), login (8), optimize (8), internal (8), disaster (8), recovery (8), high (8), agent (8), guest (8), keys (8), h4d (8), flexibility (8), dns (8), optimized (8), tpu (8), thumb (7), send (7), verify (7), checking (7), creating (7), per (7), between (7), fails (7), used (7), methods (7), maximum (7), automatic (7), both (7), level (7), setting (7), none (7), old (7), note (7), www (7), whether (7), networking (7), commitments (7), balancing (7), benchmark (7), idle (7), scale (7), deploy (7), mysql (7), maintenance (7), snapshot (7), backup (7), events (6), code (6), contains (6), distributed (6), because (6), initiate (6), replacementmethod (6), body (6), replacing (6), minimum (6), section (6), operating (6), scripts (6), errors (6), selectively (6), prevent (6), minreadysec (6), returns (6), isstable (6), resize (6), versiontarget (6), isreached (6), configurations (6), systems (6), future (6), types (6), identity (6), local (6), usage (6), security (6), migration (6), data (6), instant (6), files (6), nested (6), gpus (6), demand (6), failover (6), extension (6), transfer (6), customized (6), spot (6), understand (5), next (5), does (5), applied (5), updating (5), always (5), first (5), complete (5), keep (5), specified (5), restarted (5), current_instance_template (5), fields (5), doesn (5), surge (5), again (5), performs (5), alternatively (5), less (5), lifecycle (5), state (5), old_instance_template (5), already (5), many (5), services (5), autoscaler (5), some (5), instancestatus (5), including (5), any (5), indicates (5), active (5), expand (5), policy (5), uses (5), basic (5), environment (5), review (5), monitoring (5), databases (5), accounts (5), drivers (5), virtualization (5), nvidia (5), operations (5), placement (5), node (5), highly (5), build (5), multi (5), capacity (5), schedules (5), audit (5), symphony (5), email (5), manager (5), enhanced (5), capabilities (5), tenancy (5), restore (5), workstation (5), faq (5), flex (5), português (4), español (4), sign (4), system (4), otherwise (4), feedback (4), like (4), evenly (4), creates (4), parameters (4), targetsize (4), associated (4), different (4), performing (4), stops (4), finished (4), include (4), replaces (4), preserve (4), instead (4), examples (4), replaced (4), timestamp (4), regioninstancegroupmanagers (4), however (4), try (4), limit (4), starts (4), settings (4), dynamic (4), nics (4), interfaces (4), fully (4), health_state (4), there (4), another (4), should (4), percent (4), suspended (4), stopped (4), valid (4), preserved (4), describe (4), true (4), until (4), reached (4), omit (4), save (4), edit (4), standard (4), subset (4), above (4), deployed (4), higher (4), apis (4), development (4), authenticate (4), external (4), provider (4), plan (4), deployment (4), tools (4), issues (4), ubuntu (4), bandwidth (4), tcp (4), pmu (4), ssd (4), share (4), upgrade (4), live (4), autoscaling (4), cross (4), calendar (4), single (4), metrics (4), clusters (4), containers (4), container (4), database (4), postgresql (4), extensions (4), work (4), suspend (4), location (4), graceful (4), locations (4), plans (4), replication (4), bound (4), terms (3), started (3), content (3), apache (3), learn (3), families (3), viewing (3), distribute (3), isn (3), random (3), three (3), greater (3), number_of_zones (3), cannot (3), within (3), extreme (3), know (3), substitute (3), them (3), take (3), determine (3), customize (3), minimalaction (3), url (3), place (3), practice (3), memory (3), according (3), such (3), labels (3), tags (3), much (3), changing (3), rate (3), report (3), considering (3), successfully (3), full (3), aren (3), speed (3), stopping (3), new_instance_template (3), instance_template (3), version_name (3), last_error (3), response (3), includes (3), follow (3), explicit (3), rolls (3), previous (3), decide (3), committed (3), removed (3), verifying (3), refreshing (3), help (3), hz41 (3), modified (3), false (3), rollout (3), shows (3), affected (3), forward (3), selected (3), optional (3), potentially (3), through (3), return (3), period (3), initialdelaysec (3), waits (3), taken (3), offline (3), quota (3), advanced (3), latest (3), documentation (3), credentials (3), components (3), guides (3), infrastructure (3), observability (3), analytics (3), troubleshooting (3), encryption (3), pro (3), serial (3), patterns (3), discounts (3), cuds (3), manual (3), scalable (3), resilient (3), autoscale (3), balancer (3), ibm (3), spectrum (3), deploying (3), prepare (3), rhel (3), protect (3), certificates (3), query (3), disable (3), account (3), increase (3), schedule (3), design (3), non (3), pool (3), move (3), workstations (3), series (3), tpus (3), product (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), site (2), youtube (2), center (2), getting (2), release (2), contact (2), pricing (2), products (2), last (2), 2026 (2), utc (2), except (2), licensed (2), under (2), info (2), percentages (2), rounded (2), attempts (2), remainder (2), total (2), depending (2), situation (2), adds (2), remaining (2), versus (2), described (2), spread (2), improve (2), where (2), issuing (2), recreating (2), causes (2), quickly (2), restarts (2), finish (2), further (2), still (2), commands (2), underlying (2), reasons (2), validation (2), due (2), concurrent (2), refresh (2), afford (2), strictly (2), reads (2), order (2), pick (2), execute (2), minimize (2), cause (2), proceeding (2), seconds (2), rather (2), fast (2), sure (2), appears (2), effectively (2), 9pk4 (2), resized (2), earlier (2), making (2), deprecated (2), leave (2), performed (2), restarting (2), deleting (2), without (2), undergoing (2), sets (2), progress (2), prvp (2), w2t5 (2), listmanagedinstances (2), source (2), unhealthy (2), numerous (2), itself (2), pending (2), flags (2), tab (2), going (2), commit (2), needed (2), indicating (2), entered (2), enter (2), prompts (2), overrides (2), while (2), upgrades (2), beta (2), ready (2), here (2), common (2), preserving (2), confirm (2), shut (2), useful (2), rely (2), whenever (2), connection (2), controlling (2), maintain (2), affect (2), timer (2), conditions (2), enabled (2), rounds (2), require (2), cost (2), selective (2), applies (2), means (2), instance_template_id (2), instance_template_url (2), idp (2), federated (2), applying (2), own (2), sdk (2), languages (2), frameworks (2), costs (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), commitment (2), consumption (2), registration (2), sles (2), export (2), port (2), collecting (2), nodes (2), arm (2), core (2), rdp (2), general (2), app (2), latency (2), analyze (2), visible (2), cores (2), generation (2), underutilized (2), insights (2), utilization (2), globally (2), web (2), autohealing (2), iis (2), shared (2), reserve (2), autoscalers (2), activity (2), kubernetes (2), directory (2), redis (2), cloning (2), writer (2), alwayson (2), file (2), volumes (2), synchronization (2), switch (2), byol (2), payg (2), byos (2), guide (2), securing (2), event (2), simulate (2), topology (2), together (2), repairs (2), repair (2), failures (2), distribution (2), physical (2), cancel (2), once (2), ipv6 (2), static (2), decrease (2), consistent (2), scoped (2), copy (2), appliances (2), asynchronous (2), throughput (2), encrypt (2), format (2), mount (2), balanced (2), organization (2), user (2), rdma (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), constraints (2), accelerator (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, our, third, decade, climate, join, cookies, privacy, tech, twitter, blog, engage, training, certification, architecture, github, notes, community, forums, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, noted, java, registered, trademark, oracle, affiliates, developers, creative, commons, attribution, what, independently, difference, rolled, handled, slightly, differently, divided, divides, divide, gets, logic, numbers, specifying, equal, differences, few, exceptions, below, proportionally, nor, opposed, let, cases, entire, responding, randomly, generated, longer, notice, inspect, 1705499403, minimialaction, ddmmyyhhmm, succeed, performa, temporary, trigger, rerun, software, periodic, fresh, clear, leaks, happens, effort, particular, error, behavior, calling, mostdisruptiveallowedaction, tolerate, unnecessary, defaults, stored, description, accept, attempt, nature, disrupt, combination, low, ensures, signal, large, tentatively, pass, j1h8, ngod, staging, unknown, statuses, completely, converting, steps, strongly, recommend, way, top, unintended, consequences, beginning, caution, treats, rollback, regular, passing, relies, pendingactions, verified, suspending, starting, resumed, resuming, readded, deleted, retries, creating_without_retries, abandoning, track, instancehealth, managedinstances, 5317605642920955957, 2800161036826218547, 6789072894767812345, preservedstatefromconfig, key, preservedstatefrompolicy, autodelete, never, read_write, instance_name, column, empty, unless, h2r1, soon, redistributed, autohealer, remember, stability, depends, factors, ways, stable, least, yet, case, match, populates, read, called, planned, specification, original, configuring, property, explicitly, express, canarying, untouched, typically, continue, features, well, minimizing, users, 000, min, minutes, marking, line, changed, preserves, releases, faster, ones, checkbox, memcached, they, discovery, result, loses, proactively, deletes, swaps, completed, done, diagram, 3600, hour, checks, declares, waiting, verification, remains, autohealingpolicies, amount, satisfied, resolve, ensure, proceed, removes, middle, count, toward, ignored, force, works, enough, speeds, billed, price, sheet, too, actively, resizes, complex, sections, multiplied, contain, follows, expects, desired, post, function, declarative, initial, successful, indicate, succeeded, was, intent, things, mind, various, aspects, long, affects, just, portion, gradually, intended, skips, supported, equivalently, limitations, haven, verifies, selecting, installed, previously, init, installation, initialize, removing, begin, known, input, completes, those, added, maintains, document, describes, categorize, preferences, stay, organized, collections, home, renewal, nvme, resizing, pay, output, diagnostic, sudoers, screenshots, generate, bug, blackwell, soft, lockups, bus, locks, rescue, inaccessible, dumps, kernel, panic, fstab, unresponsive, suspension, reboots, shutdowns, connectivity, tips, dpdk, resiliency, communication, reduce, compact, idpf, interface, irdma, driver, nic, threads, sustained, merge, split, extend, renew, purchase, savings, overcommit, cpus, floating, reliable, udp, backends, routing, scaling, consuming, consume, combine, cud, allow, sharing, decisions, signals, serving, predictions, organize, replica, states, observe, reports, tensorflow, inference, tensorrt5, learning, monte, carlo, spark, forwarding, others, integrate, clustering, exchange, 2016, sharepoint, strategies, passive, inactive, setups, built, integrations, were, transition, hammerdb, bucket, aws, ec2, pacemaker, s2d, block, netapp, hot, standby, drbd, architectures, client, private, address, mailjet, mailgun, sendgrid, sending, blue, green, deployments, lamp, joomla, asp, net, interactive, mongodb, flask, terraform, servers, over, mtls, generator, virtio, rng, accurate, protocol, ntp, append, els, restrictions, packages, deprecate, family, trusted, red, hat, knowledgebase, functionality, risks, vpc, controls, confidential, kek, secure, expiration, shielded, attributes, predefined, handle, notices, faulty, unmanaged, turn, off, alternate, repairing, override, accelerate, outage, rebalance, reenable, redistribution, shape, define, accidental, deletion, rename, reset, resume, referrers, uuid, recover, corrupted, duplicate, clones, alerts, backups, vss, regionally, protection, considerations, synchronous, consistency, failback, replicate, provisioned, iops, limits, evaluate, kms, customer, supplied, symbolic, links, device, ram, attach, exapools, ptr, record, failure, rates, restrict, automate, password, powershell, sac, securely, apps, root, vpn, bastion, iap, browser, connections, networks, iso, imported, prerequisites, importing, exporting, bring, path, detach, reattach, constraint, accounting, provision, slurm, reserved, team, slice, slices, scenarios, deterministic, base, requirements, aci, configured, preempted, historical, alternative, similar, displays, ops, logging, subnet, public, gpudirect, ultra, platform, hostname, quickstarts, iam, roles, office, licensing, premium, strategy, gemini, bare, metal, accelerators, platforms, scores, purpose, discover, free, skip, main,

Text of the page (random words):
populates a read only field called status that contains a versiontarget isreached flag and an isstable flag you can use the gcloud cli or rest to access these flags you can also use the google cloud console to see the current and planned number of instances being updated permissions required for this task to perform this task you must have the following permissions compute instancegroupmanagers get on the mig console you can monitor a rolling update for a group by going to the group s details page in the google cloud console go to the instance groups page go to instance groups select the managed instance group that you want to monitor the overview page for the group shows the template that each instance is using to view the details click the details tab in the instance template section you can see the current and target number of instances for each instance template to view the update settings click update parameters to expand gcloud use the describe command gcloud compute instance groups managed describe instance_group_name zone zone region region you can also use the gcloud compute instance groups managed wait until command with the version target reached flag to wait until status versiontarget isreached is set to true for the group gcloud compute instance groups managed wait until instance_group_name version target reached zone zone region region rest call the get method on a regional or zonal mig resource get https compute googleapis com compute v1 projects project_id regions region instancegroupmanagers instance_group_name get verify whether an update rollout is complete verify whether the rollout of an update is complete by checking the value of the mig s status versiontarget isreached field status versiontarget isreached set to true indicates that all vm instances have been or are being created using the target version status versiontarget isreached set to false indicates that at least one vm is not yet using the target version or in the case of a canary update false indicates that the number of vms using a target version doesn t match its target size note to verify that the update rollout is complete and also that all vm instances in the group are running and healthy check both the status isstable and status versiontarget isreached flags check whether a managed instance group is stable verify that all instances in a managed instance group are running and healthy by checking the value of the group s status isstable field status isstable set to false indicates that changes are active pending or that the mig itself is being modified status isstable set to true indicates the following none of the instances in the mig are undergoing any type of change and the currentaction for all instances is none no changes are pending for instances in the mig the mig itself is not being modified remember that the stability of a mig depends on numerous factors because a mig can be modified in numerous ways for example you make a request to roll out a new instance template you make a request to create delete resize or update instances in the mig an autoscaler requests to resize the mig an autohealer resource is replacing one or more unhealthy instances in the mig in a regional mig some of the instances are being redistributed as soon as all actions are finished status isstable is set to true again for that mig current actions on instances to view details about instances in a mig including their status and any current actions being performed by the group use the google cloud cli or rest permissions required for this task to perform this task you must have the following permissions compute instancegroupmanagers get on the group compute instancegroupmanagers list on the group gcloud all managed instances to check the status and current actions on all instances in the group use the list instances command gcloud compute instance groups managed list instances instance_group_name zone zone region region the command returns a list of instances in the group including their status current actions and other details name vm instances 9pk4 zone us central1 f status health_state action creating instance_template my new template version_name last_error name vm instances h2r1 zone us central1 f status stopping health_state action deleting instance_template my old template version_name last_error the health_state column appears empty unless you have set up health checking a specific managed instance to check the status and current action for a specific instance in the group use the describe instance command gcloud compute instance groups managed describe instance instance_group_name instance instance_name zone zone region region the command returns details about the instance including instance status current action and for stateful migs preserved state currentaction none id 6789072894767812345 instance https www googleapis com compute v1 projects example project zones us central1 a instances example mig hz41 instancestatus running name example mig hz41 preservedstatefromconfig metadata example key example value preservedstatefrompolicy disks persistent disk 0 autodelete never mode read_write source https www googleapis com compute v1 projects example project zones us central1 a disks example mig hz41 version instancetemplate https www googleapis com compute v1 projects example project global instancetemplates example template rest call the listmanagedinstances method on a regional or zonal mig resource for example to see details about the instances in a zonal mig resource you can make the following request get https compute googleapis com compute v1 projects project_id zones zone instancegroupmanagers instance_group_name listmanagedinstances the call returns a list of instances for the mig including each instance s instancestatus and currentaction managedinstances instance https www googleapis com compute v1 projects example project zones us central1 f instances vm instances prvp instancestatus running currentaction refreshing id 5317605642920955957 version instancetemplate https www googleapis com compute v1 projects example project global instancetemplates example template name vm instances prvp instance https www googleapis com compute v1 projects example project zones us central1 f instances vm instances w2t5 instancestatus running currentaction refreshing id 2800161036826218547 version instancetemplate https www googleapis com compute v1 projects example project global instancetemplates example template name vm instances w2t5 if you set up health checking then the response also includes the instancehealth field to see a list of valid instancestatus field values see vm instance lifecycle if an instance is undergoing some type of change the mig sets the instance s currentaction field to one of the following actions to help you track the progress of the change otherwise the currentaction field is set to none possible currentaction values are abandoning the instance is being removed from the mig creating the instance is in the process of being created creating_without_retries the instance is being created without retries if the instance isn t created on the first try the mig doesn t try to replace the instance again deleting the instance is in the process of being deleted recreating the instance is being replaced refreshing the instance is being removed from its current target pools and being readded to the list of current target pools this list might be the same or different from existing target pools restarting the instance is in the process of being restarted using the stop and start methods resuming the instance is in the process of being resumed after being suspended starting the instance is in the process of being started after being stopped stopping the instance is being stopped suspending the instance is being suspended verifying the instance has been created and is in the process of being verified none no actions are being performed on the instance note the pendingactions field is deprecated and is to be removed contact cloud updater feedback google com to leave feedback if your workload relies on this field roll back an update there is no explicit command for rolling back an update to a previous version but if you decide to roll back an update either a fully committed update or a canary update you can do so by making a new update request and passing in the instance template that you want to roll back to gcloud for example the following gcloud cli command rolls back an update as fast as possible replace old_instance_template with the name of the instance template you want to roll back to gcloud compute instance groups managed rolling action start update instance_group_name version template old_instance_template max unavailable 100 zone zone region region rest call the patch method on a regional or zonal mig resource in the request body specify the earlier instance template as a version patch https compute googleapis com compute v1 projects project_id regions region instancegroupmanagers instance_group_name updatepolicy maxunavailable percent 100 versions instancetemplate global instancetemplates old_instance_template old instance template for a regional mig with less than 10 instances you must use a fixed value for maxunavailable and set the value to the number of instances in the group the updater treats a rollback request the same as a regular update request so you can specify additional update options caution for canary updates we strongly recommend fully rolling back canary updates before you try to canary another version there is no way to selectively choose which instances are updated based on which instance template and performing another canary update on top of an existing update can cause unintended consequences as a best practice you should fully roll back a canary update first and restart the canary process again from the beginning stop an update there is no explicit method or command to stop an update you can change an update from proactive to opportunistic and if the group is not being resized by other services like autoscaler the change to opportunistic effectively stops the update to change an update from proactive to opportunistic by using the gcloud cli run the following command gcloud compute instance groups managed rolling action stop proactive update instance_group_name zone zone region region to stop the update completely after converting it from proactive to opportunistic follow these steps make a request to determine how many instances have been updated gcloud compute instance groups managed list instances instance_group_name zone zone region region the gcloud cli returns a response that includes a list of instances in the group and their current statuses name zone status health_state action instance_template version_name last_error vm instances 9pk4 us central1 f running healthy none example new template vm instances j1h8 us central1 f running healthy none example old template vm instances ngod us central1 f staging unknown creating example new template in this example two instances have already been updated next make a request to perform a new update but pass in the number of instances that have already been updated as the target size gcloud compute instance groups managed rolling action start update instance_group_name version template old_instance_template canary version template new_instance_template target size 2 zone zone region region to the updater this update appears complete so no other instances are updated effectively stopping the update control the speed of a rolling update by default when you make an update request the updater performs the update as fast as possible if you aren t sure you want to apply an update fully or are tentatively testing your changes you can control the speed of the update by using the following methods start a canary update rather than a full update set a large minreadysec value setting this value causes the updater to wait this number of seconds before considering the instance successfully updated and proceeding to the next instance enable health checking to cause the updater to wait for your application to start and to report a healthy signal before considering the instance successfully updated and proceeding to the next instance set low maxunavailable and maxsurge values this ensures that only a minimal number of instances are updated at a time selectively update instances in a mig instead of using an automated update you can also use a combination of these methods to control the rate of your update control the disruption level during a rolling update depending on the nature of an update it might disrupt an instance s lifecycle state for example changing an instance s boot disk requires replacing the instance you can control the level of disruption during a rolling update by setting the following options minimal action use this option to minimize disruption as much as possible or to apply a more disruptive action than is necessary to limit disruption as much as possible set the minimal action to refresh if your update requires a more disruptive action compute engine performs the necessary action to execute the update to apply a more disruptive action than is strictly necessary set the minimal action to restart or replace for example compute engine does not need to restart a vm to change its metadata but if your application reads instance metadata only when a vm is restarted you can set the minimal action to restart in order to pick up metadata changes most disruptive allowed action use this option to prevent an update if it requires more disruption than you can afford if your update requires a more disruptive action than you set with this flag the update request fails for example if you set the most disruptive allowed action to restart then an attempt to update the boot disk image fails because that update requires instance replacement a more disruptive action than a restart both of these options accept the following values value description which instance properties can be updated refresh don t stop the instance additional disks dynamic network interfaces nics instance metadata labels tags restart stop the instance and start it again additional disks dynamic nics instance metadata labels tags machine type replace default replace the instance according to the replacement method option all instance properties stored in the instance template or per instance configuration the most disruptive allowed action can t be less disruptive than the minimal action when you automatically roll out updates the following defaults apply the default minimal action is replace if you want to prevent unnecessary disruption set the minimal action to be less disruptive the default most disruptive allowed action is replace if you cannot tolerate such disruption set the most disruptive allowed action to be less disruptive you can change the default behavior by using the compute engine api t...