[AVM Module Issue]: 'windowsProfile' not supported for AKS AVM deployment. Can't deploy Windows Node Pools

[BramReijnders]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/container-service/managed-cluster

(Optional) Module Version

0.10.1

Description

It is possible to define Windows as osType and osSKU at agent pool level. However, it is mandatory to define a username and password in the 'windowsProfile' configuration of the initial AKS deployment to be allowed to deploy any windows node pool on the cluster. This configuration is missing in the current AVM module.

To support Windows Node Pools the 'windowsProfile' object needs to be available in the AVM module.

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[avm-team-linter]

@BramReijnders, thanks for submitting this issue for the avm/res/container-service/managed-cluster module!

Important

A member of the @Azure/avm-res-containerservice-managedcluster-module-owners-bicep or @Azure/avm-res-containerservice-managedcluster-module-contributors-bicep team will review it soon!

[JPEasier]

Hi @BramReijnders, I will check the issue and get back to you.

[microsoft-github-policy-service]

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!