Skip to content

Commit 1444b0f

Browse files
authored
Update virtual-machine-scale-sets-use-availability-zones.md
1 parent a603575 commit 1444b0f

File tree

1 file changed

+0
-7
lines changed

1 file changed

+0
-7
lines changed

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-use-availability-zones.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -253,13 +253,6 @@ You can update the zones parameter and the scale set capacity in the same ARM te
253253

254254
When you are satisfied that the new instances are ready, scale in your scale set to remove the original regional instances. You can either manually delete the specific regional instances, or scale in by reducing the scale set capacity. When scaling in via reducing scale set capacity, the platform will always prefer removing the regional instances, then follow the scale in policy.
255255

256-
#### Automate with Rolling upgrades + MaxSurge
257-
258-
With [Rolling upgrades + MaxSurge](virtual-machine-scale-sets-upgrade-policy.md), new zonal instances are created and brought up-to-date with the latest scale model in batches. Once a batch of new instances is added to the scale set and report as healthy, a batch of old instances are automated removed from the scale set. Upgrades continue until all instances are brought up-to-date.
259-
260-
> [!IMPORTANT]
261-
> Rolling upgrades with MaxSurge is currently under Public Preview. It is only available for VMSS Uniform Orchestration Mode.
262-
263256
### Known issues and limitations
264257

265258
* The feature is targeted to stateless workloads on Virtual Machine Scale Sets.

0 commit comments

Comments
 (0)