Skip to content

Fix wrong VM size for windows nodepool in tutorial #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 10, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -320,14 +320,15 @@ the az Azure command line tool is out of date.

In the previous section, we created an AKS cluster with a linux node. However, for our recording
bot application, we actually need a windows node instead. Let us create two new windows nodes of
the `standard_d2s_v3`-series:
the `standard_d4_v3`-series, this series is also available in most Microsoft Azure regions
and meets the requirement of two physical cpu cores specified by the media SDK:

```powershell
az aks nodepool add
--cluster-name recordingbotcluster
--name win22
--resource-group recordingbottutorial
--node-vm-size standard_d2s_v3
--node-vm-size standard_d4_v3
--node-count 2
--os-type Windows
--os-sku Windows2022
Expand Down Expand Up @@ -388,7 +389,7 @@ This command also needs some time to complete, our result output should look sim
"maxSurge": null,
"nodeSoakDurationInMinutes": null
},
"vmSize": "standard_d2s_v3",
"vmSize": "standard_d4_v3",
"vnetSubnetId": null,
"workloadRuntime": null
}
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -210,7 +210,7 @@ After that the execution of the command takes some time and results in an output
"maxSurge": null,
"nodeSoakDurationInMinutes": null
},
"vmSize": "standard_d2s_v3",
"vmSize": "standard_d4_v3",
"vnetSubnetId": null,
"windowsProfile": {},
"workloadRuntime": null
Expand Down
Loading