Skip to content

Commit a41215e

Browse files
authored
Update cannot-scale-cluster-autoscaler-enabled-node-pool.md
1 parent f5f56d4 commit a41215e

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

support/azure/azure-kubernetes/create-upgrade-delete/cannot-scale-cluster-autoscaler-enabled-node-pool.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,9 @@ You receive an error message that resembles the following message:
2222
2323
## Troubleshooting checklist
2424

25-
Azure Kubernetes Service (AKS) uses virtual machine (VM) scale sets-based agent pools. These pools contain cluster nodes and [cluster autoscaling capabilities](/azure/aks/cluster-autoscaler), if they're enabled.
25+
Azure Kubernetes Service (AKS) uses Azure Virtual Machine Scale Sets-based agent pools. These pools contain cluster nodes and [cluster autoscaling capabilities](/azure/aks/cluster-autoscaler), if they're enabled.
2626

27-
### Check that the cluster VM scale set exists
27+
### Check that the cluster virtual machine scale set exists
2828

2929
1. Sign in to the [Azure portal](https://portal.azure.com).
3030
1. Find the node resource group by searching for the following names:
@@ -35,18 +35,18 @@ Azure Kubernetes Service (AKS) uses virtual machine (VM) scale sets-based agent
3535
> [!NOTE]
3636
> When you create a cluster, AKS automatically creates a second resource group to store the AKS resources. For more information, see [Why are two resource groups created with AKS?](/azure/aks/faq#why-are-two-resource-groups-created-with-aks)
3737
38-
1. Check the list of resources to make sure that a VM scale set exists.
38+
1. Check the list of resources to make sure that a virtual machine scale set exists.
3939

40-
## Cause 1: The cluster VM scale set was deleted
40+
## Cause 1: The cluster virtual machine scale set was deleted
4141

42-
If you delete the VM scale set that's attached to the cluster, this action causes the cluster autoscaler to fail. It also causes issues when you provision resources such as nodes and pods.
42+
If you delete the virtual machine scale set that's attached to the cluster, this action causes the cluster autoscaler to fail. It also causes issues when you provision resources such as nodes and pods.
4343

4444
> [!NOTE]
45-
> Modifying any resource under the node resource group in the AKS cluster is an unsupported action and will cause cluster operation failures. You can prevent changes from being made to the node resource group by [blocking users from modifying resources](/azure/aks/cluster-configuration#fully-managed-resource-group-preview) that are managed by the AKS cluster.
45+
> Modifying any resource under the node resource group in the AKS cluster is an unsupported action and causes cluster operation failures. You can prevent changes from being made to the node resource group by [blocking users from modifying resources](/azure/aks/cluster-configuration#fully-managed-resource-group-preview) that are managed by the AKS cluster.
4646
4747
### Reconcile node pool
4848

49-
If the cluster VM scale set is accidentally deleted, you can reconcile the node pool by using `az aks nodepool update`:
49+
If the cluster virtual machine scale set is accidentally deleted, you can reconcile the node pool by using `az aks nodepool update`:
5050

5151
```bash
5252
# Update Node Pool Configuration
@@ -80,7 +80,7 @@ Deleting the cluster node resource group causes issues when you provision the in
8080

8181
## Solution: Update the cluster to the goal state without changing the configuration
8282

83-
To resolve this issue, run the following command to recover the deleted VM scale set or any tags (missing or modified).
83+
To resolve this issue, run the following command to recover the deleted virtual machine scale set or any tags (missing or modified).
8484

8585
> [!NOTE]
8686
> It might take a few minutes until the operation finishes.

0 commit comments

Comments
 (0)