Skip to content

Commit ee7604b

Browse files
committed
Update virtual-machine-scale-sets-maxsurge.md
1 parent ec9e845 commit ee7604b

File tree

1 file changed

+5
-9
lines changed

1 file changed

+5
-9
lines changed

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maxsurge.md

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,11 @@ Rolling upgrades with MaxSurge can help improve service uptime during upgrade ev
3434
|**Prioritize unhealthy instances** | Tells the scale set to upgrade instances marked as unhealthy before upgrading instances marked as healthy. <br><br>Example: If some instances in your scale set that show as failed or unhealthy when a rolling upgrade begins, the scale set updates those instances first. |
3535
|**Enable cross-zone upgrade** | Allows the scale set to ignore Availability Zone boundaries when determining batches. |
3636

37+
## Considerations
38+
39+
When using rolling upgrades with MaxSurge, new virtual machines are created using the latest scale set model to replace virtual machines using the old scale set model. These newly created virtual machines counts towards your overall core quota. Additionally, these new virtual machines will have new IP addresses and be placed into an existing subnet. You also need to have enough IP address quota and subnet space available to deploy these newly created virtual machines.
40+
41+
During the rolling upgrade processes, Azure performs a quota check before each new batch. If that quota check fails, the rolling upgrade will be canceled. You can restart a rolling upgrade by making a new change to the scale set model or triggering a generic model update. For more information, see [restart a rolling upgrade](virtual-machine-scale-sets-configure-rolling-upgrades.md#restart-a-rolling-upgrade)
3742

3843
## MaxSurge vs in place upgrades
3944

@@ -124,15 +129,6 @@ Yes. All upgrade policies including rolling upgrades with MaxSurge are generally
124129
### Is MaxSurge generally available for Virtual Machine Scale Sets with Flexible Orchestration?
125130
No. All upgrade policies including rolling upgrades with MaxSurge are in Public Preview for Virtual Machine Scale Sets with Flexible Orchestration.
126131

127-
### Do MaxSurge upgrades require more quota?
128-
Yes. When using rolling upgrades with MaxSurge, new virtual machines are created using the latest scale set model to replace virtual machines using the old scale set model. These newly created virtual machines counts towards your overall core quota.
129-
130-
### Do MaxSurge upgrades require additional IP addresses?
131-
Yes. These newly created virtual machines have new IP addresses and count towards your total allowed IP addresses available per your subscription.
132-
133-
### Do MaxSurge upgrades require additional subnet space?
134-
Yes. These newly created virtual machines have new IP addresses and there needs to be enough space available in the specified subnet to be added.
135-
136132
### What triggers a MaxSurge upgrade?
137133
Any changes that result in an update to the scale set model result in a MaxSurge upgrade. This includes upgrades that generally don't require a restart such as adding Data Disks.
138134

0 commit comments

Comments
 (0)