From 184b8f7e71d92e00b66e133ead7ed5d7258c8dab Mon Sep 17 00:00:00 2001 From: Kimberly Yip Chang Date: Sun, 22 Nov 2020 22:37:42 -0500 Subject: [PATCH] Add enableCrossZoneUpgrade and prioritizeUnhealthyInstances properties to RollingUpgradePolicy for VMSS (#11184) --- .../Microsoft.Compute/stable/2020-12-01/compute.json | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/specification/compute/resource-manager/Microsoft.Compute/stable/2020-12-01/compute.json b/specification/compute/resource-manager/Microsoft.Compute/stable/2020-12-01/compute.json index e893556c0159..44f12ab3b0c8 100644 --- a/specification/compute/resource-manager/Microsoft.Compute/stable/2020-12-01/compute.json +++ b/specification/compute/resource-manager/Microsoft.Compute/stable/2020-12-01/compute.json @@ -9572,6 +9572,14 @@ "pauseTimeBetweenBatches": { "type": "string", "description": "The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format. The default value is 0 seconds (PT0S)." + }, + "enableCrossZoneUpgrade": { + "type": "boolean", + "description": "Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size." + }, + "prioritizeUnhealthyInstances": { + "type": "boolean", + "description": "Upgrade all unhealthy instances in a scale set before any healthy instances." } }, "description": "The configuration parameters used while performing a rolling upgrade."