Skip to content

Commit f3dd66c

Browse files
committed
Fixes
1 parent 9a965d6 commit f3dd66c

File tree

1 file changed

+19
-21
lines changed

1 file changed

+19
-21
lines changed

AKS-Arc/deploy-ai-model.md

Lines changed: 19 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -55,39 +55,37 @@ az aksarc update --resource-group <Resource_Group_name> --name <Cluster_Name> --
5555

5656
## Add a GPU node pool
5757

58-
Before you add a GPU node pool, make sure that Azure Local is enabled with a supported GPU such as A2, T4, or A16, and that the GPU drivers are installed on all the host nodes. To add a GPU node pool, follow these steps:
58+
1. Before you add a GPU node pool, make sure that Azure Local is enabled with a supported GPU such as A2, T4, or A16, and that the GPU drivers are installed on all the host nodes. To add a GPU node pool, follow these steps:
5959

60-
### [Azure portal](#tab/portal)
60+
### [Azure portal](#tab/portal)
6161

62-
Sign in to the Azure portal and find your AKS Arc cluster. Under **Settings > Node pools**, select **Add**. Fill in the other required fields, then create the node pool.
62+
Sign in to the Azure portal and find your AKS Arc cluster. Under **Settings > Node pools**, select **Add**. Fill in the other required fields, then create the node pool.
6363

64-
### [Azure CLI](#tab/azurecli)
64+
### [Azure CLI](#tab/azurecli)
6565

66-
To create a GPU node pool using Azure CLI, run the following command.
66+
To create a GPU node pool using Azure CLI, run the following command.
6767

68-
```azurecli
69-
az aksarc nodepool add --resource-group <Resource_Group_name> --cluster-name <Cluster_Name> --name <Node_Pool_Name> --node-vm-size <GPU_VM_SKU> --node-count 1
70-
```
71-
72-
---
68+
```azurecli
69+
az aksarc nodepool add --resource-group <Resource_Group_name> --cluster-name <Cluster_Name> --name <Node_Pool_Name> --node-vm-size <GPU_VM_SKU> --node-count 1
70+
```
7371

74-
After the node pool is provisioned, you can confirm whether the node is successfully provisioned using the node pool name.
72+
---
7573

76-
### [Azure CLI](#tab/azurecli)
74+
1. After the node pool is provisioned, you can confirm whether the node is successfully provisioned using the node pool name.
7775

78-
```azurecli
79-
kubectl get nodes --show-labels | grep "msft.microsoft/nodepool-name=.*<Node_Pool_Name>" | awk '{print $1}'
80-
```
76+
```azurecli
77+
kubectl get nodes --show-labels | grep "msft.microsoft/nodepool-name=.*<Node_Pool_Name>" | awk '{print $1}'
78+
```
8179

82-
### [PowerShell](#tab/powershell)
80+
For PowerShell, you can use the following command:
8381

84-
```powershell
85-
kubectl get nodes --show-labels | Select-String "msft.microsoft/nodepool-name=.*<Node_Pool_Name>" | ForEach-Object { ($_ -split '\s+')[0] }
86-
```
82+
```powershell
83+
kubectl get nodes --show-labels | Select-String "msft.microsoft/nodepool-name=.*<Node_Pool_Name>" | ForEach-Object { ($_ -split '\s+')[0] }
84+
```
8785

88-
---
86+
---
8987

90-
Label the newly provisioned GPU node so the inference workspace can be deployed to the node in the next step. You can make sure the label is applied using `kubectl get nodes`.
88+
1. Label the newly provisioned GPU node so the inference workspace can be deployed to the node in the next step. You can make sure the label is applied using `kubectl get nodes`.
9189

9290
```azurecli
9391
kubectl label node moc-l36c6vu97d5 apps=llm-inference

0 commit comments

Comments
 (0)