Azure-docs: Creating a Windows AKS cluster w/ an ARM template

[neilhuiz]

I've spent the last couple days trying to get a Windows AKS cluster set up using an ARM template. I've succeeded in creating a cluster with only one Linux node pool. When I include both a Linux and a Windows node pool profile, though, the node pools are created in the portal, the node pool resource group is created, however, the VMSS objects are never created.

My current workaround is to create a single pool cluster, then use az aks nodepool add to add a second pool with the Windows OS type. Thankfully, this seems to work nicely but I'd really rather be able to make a cluster all in one deployment.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 6de70aec-9ebe-5655-6657-5c171de374b1
• Version Independent ID: c9eb35c8-8703-511b-987b-e2a441be2e47
• Content: Preview - Create a Windows Server container on an Azure Kubernetes Service (AKS) cluster
• Content Source: articles/aks/windows-container-cli.md
• Service: container-service
• GitHub Login: @mlearned
• Microsoft Alias: mlearned

[Karishma-Tiwari-MSFT]

Thanks for the question. We are currently investigating and will update you shortly.

[Karishma-Tiwari-MSFT]

@sauryadas Can you please share your insights on this question. Thanks :)

[MikkelHegn]

We do not support creating multiple node pools in one deployment at this point in time, this is coming soon however - @jluk.

Regarding

When I include both a Linux and a Windows node pool profile, though, the node pools are created in the portal, the node pool resource group is created, however, the VMSS objects are never created.

Do you have the default / first node pool successfully created?

[neilhuiz]

Thanks for the update, @MikkelHegn. I'll look forward to this feature in the future. It would make deploying Windows clusters, where two node pools appear to be a requirement, so much simpler.

Do you have the default / first node pool successfully created?

No, I do not. When I include two node pools in my ARM template (i.e. two entries under agentPoolProfiles), neither of the pools' machines are created. The node pools show up in the portal when you browse the details of the cluster, the resource group meant to contain them is created, however availability sets (or VMSS's) are not created in the node resource group. Running kubectl get nodes succeeds but returns zero nodes. The cluster is unusable at that point.

[bobhlo]

Look forward to be able to deploy multiple node pools with one deployment. Experienced the same issue(Linux and Windows node pools show up but VMSS not created in the node resource group) with Terraform.

[Karishma-Tiwari-MSFT]

@neilhuiz and @bobhlo Thank you for providing valuable feedback.
As shared above, We do not support creating multiple node pools in one deployment at this point in time, but this is coming soon. We will share here once we have an update on this functionality.
We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.

[foobarnum]

You closed this without updating as to when this feature was planned. When is this limitation going to be removed

[MikkelHegn]

This is possible today.

[nreddipalle]

I am trying to find a working ARM template sample for Windows AKS. @neilhuiz.. would you mind sharing a sample. thanks

[Karishma-Tiwari-MSFT]

This doc might help: https://docs.microsoft.com/en-us/azure/aks/use-multiple-node-pools#manage-node-pools-using-a-resource-manager-template