You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/api-overview/resources/vm-scale-set.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,14 @@ The Virtual Machine Scale Set builder (`vmss`) creates a virtual machine scale s
32
32
| vmss | osupgrade_automatic_rollback | Whether OS image rollback feature should be enabled. Enabled by default. |
33
33
| vmss | osupgrade_rolling_upgrade | Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Default value is false. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. |
34
34
| vmss | osupgrade_rolling_upgrade_deferral | Indicates whether Auto OS Upgrade should undergo deferral. Deferred OS upgrades will send advanced notifications on a per-VM basis that an OS upgrade from rolling upgrades is incoming, via the IMDS tag 'Platform.PendingOSUpgrade'. The upgrade then defers until the upgrade is approved via an ApproveRollingUpgrade call. |
35
+
| vmss | rolling_upgrade_enable_cross_zone_upgrade | Allow VMSS to ignore Availability Zone boundaries when constructing upgrade batches. Allows Azure to spread out batches across different zones. |
36
+
| vmss | rolling_upgrade_max_batch_instance_percent | The maximum percentage of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. Should be between 5 and 100. |
37
+
| vmss | rolling_upgrade_max_surge | Create new instances temporarily to replace old ones during upgrade. Helps maximize availability during rolling upgrades. |
38
+
| vmss | rolling_upgrade_max_unhealthy_instance_percent | The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy before the rolling upgrade aborts. |
39
+
| vmss | rolling_upgrade_max_unhealthy_upgraded_instance_percent | The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. |
40
+
| vmss | rolling_upgrade_pause_time_between_batches | 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 (e.g. PT5M for 5 minutes). |
41
+
| vmss | rolling_upgrade_prioritize_unhealthy_instances | Upgrade all unhealthy instances in a scale set before any healthy instances. |
42
+
| vmss | rolling_upgrade_rollback_failed_instances_on_policy_breach | Rollback failed instances to previous model if the Rolling Upgrade policy is violated. |
35
43
| applicationHealthExtension | vmss | When adding the extension as a resource, this specifies the VM scale set it should be applied to. |
36
44
| applicationHealthExtension | os | Operating system (Linux or Windows) to install the correct extension for that OS. |
37
45
| applicationHealthExtension | protocol | Protocol (TCP, HTTP, or HTTPS) to probe, and if specifying HTTP or HTTPS, include the path. |
0 commit comments