The maximum number (or percentage) of VMs per zone to disrupt at any given moment. The number of VMs calculated from multiplying the percentage by the total number of VMs in a zone is rounded up.
During patching, a VM is considered disrupted from the time the agent is notified to begin until patching has completed. This disruption time includes the time to complete reboot and any post-patch steps.
A VM contributes to the disruption budget if its patching operation fails either when applying the patches, running pre or post patch steps, or if it fails to respond with a success notification before timing out. VMs that are not running or do not have an active agent do not count toward this disruption budget.
For zone-by-zone rollouts, if the disruption budget in a zone is exceeded, the patch job stops, because continuing to the next zone requires completion of the patch process in the previous zone.
For example, if the disruption budget has a fixed value of 10, and 8 VMs fail to patch in the current zone, the patch job continues to patch 2 VMs at a time until the zone is completed. When that zone is completed successfully, patching begins with 10 VMs at a time in the next zone. If 10 VMs in the next zone fail to patch, the patch job stops.
Mode
Type of the rollout.
Enums
MODE_UNSPECIFIED
Mode must be specified.
ZONE_BY_ZONE
Patches are applied one zone at a time. The patch job begins in the region with the lowest number of targeted VMs. Within the region, patching begins in the zone with the lowest number of targeted VMs. If multiple regions (or zones within a region) have the same number of targeted VMs, a tie-breaker is achieved by sorting the regions or zones in alphabetical order.
CONCURRENT_ZONES
Patches are applied to VMs in all zones at the same time.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-28 UTC."],[[["\u003cp\u003ePatch rollout configurations control how patches are applied to virtual machines (VMs), including concurrency management.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003emode\u003c/code\u003e field specifies whether patches are applied \u003ccode\u003eZONE_BY_ZONE\u003c/code\u003e or to \u003ccode\u003eCONCURRENT_ZONES\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003edisruptionBudget\u003c/code\u003e defines the maximum number or percentage of VMs per zone that can be disrupted at any time during patching.\u003c/p\u003e\n"],["\u003cp\u003eDisrupted VMs during patching include those from the moment of agent notification to patching completion and post-patch steps, also including failing VMs.\u003c/p\u003e\n"],["\u003cp\u003ePatch jobs will halt if the \u003ccode\u003edisruptionBudget\u003c/code\u003e is exceeded in a given zone, for \u003ccode\u003eZONE_BY_ZONE\u003c/code\u003e mode.\u003c/p\u003e\n"]]],[],null,[]]
