Skip to content

Commit 3e8aa65

Browse files
committed
updated language
1 parent bb0732e commit 3e8aa65

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/aks/use-multiple-node-pools.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -301,7 +301,7 @@ AKS offers a separate feature to automatically scale node pools with a feature c
301301

302302
## Resize a node pool
303303

304-
To increase of number of deployments or run a larger workload, you may want to change the VMSS plan or resize AKS instances. However, you should not do any direct customizations to these nodes using the IaaS APIs or resources, as any custom changes that are not done via the AKS API will not persist through an upgrade, scale, update or reboot. This means resizing your AKS instances in this manner is not supported.
304+
To increase of number of deployments or run a larger workload, you may want to change the virtual machine scale set plan or resize AKS instances. However, you should not do any direct customizations to these nodes using the IaaS APIs or resources, as any custom changes that are not done via the AKS API will not persist through an upgrade, scale, update or reboot. This means resizing your AKS instances in this manner is not supported.
305305

306306
The recommended method to resize a node pool to the desired SKU size is as follows:
307307

@@ -310,7 +310,7 @@ The recommended method to resize a node pool to the desired SKU size is as follo
310310
* Remove the old node pool.
311311

312312
> [!IMPORTANT]
313-
> This method is specific to VMSS-based AKS clusters. When using VMAS, you are limited to only one node pool per cluster.
313+
> This method is specific to virtual machine scale set-based AKS clusters. When using virtual machine availability sets, you are limited to only one node pool per cluster.
314314
315315
### Create a new node pool with the desired SKU
316316

@@ -388,7 +388,7 @@ kubectl get pods -o wide -A
388388

389389
### Remove the existing node pool
390390

391-
To delete the existing node pool, see [the below steps](#delete-a-node-pool)
391+
To delete the existing node pool, see the section on [Deleting a node pool](#delete-a-node-pool).
392392

393393
After completion, the final result is the AKS cluster having a single, new node pool with the new, desired SKU size and all the applications and pods properly running.
394394

0 commit comments

Comments
 (0)