Skip to content

Commit 3263b4d

Browse files
authored
Combine suggested change into previous paragraph
In order to keep the tip from looking like a step in the process, I changed the text and added it inline in the previous paragraph.
1 parent 717a969 commit 3263b4d

1 file changed

Lines changed: 1 addition & 7 deletions

File tree

docs/big-data-cluster/deploy-on-aks.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -127,13 +127,7 @@ Choose the latest available version for your cluster. Record the version number.
127127
--kubernetes-version <version number>
128128
```
129129

130-
You can increase or decrease the number of Kubernetes agent nodes by changing the `--node-count <n>` where `<n>` is the number of agent nodes you want to use. This does not include the master Kubernetes node, which is managed behind the scenes by AKS. The previous example only uses a single node for evaluation purposes.
131-
132-
You can use the following command to pick the appropriate vm-size that is available in your Azure regions and matches your workload requirements:
133-
134-
```azurecli
135-
az vm list-sizes --location westus2 -o table
136-
```
130+
You can increase or decrease the number of Kubernetes agent nodes by changing the `--node-count <n>` where `<n>` is the number of agent nodes you want to use. This does not include the master Kubernetes node, which is managed behind the scenes by AKS. The previous example only uses a single node for evaluation purposes. You can also change the `--node-vm-size` to select an appropriate virtual machine size that matches your workload requirements. Use the `az vm list-sizes --location westus2 -o table` command to list available virtual machine sizes in your region.
137131

138132
After several minutes, the command completes and returns JSON-formatted information about the cluster.
139133

0 commit comments

Comments
 (0)