Se podnet

[samaea]

PR Summary

Addressing customer issue:- #569.

The Azure CNI networking for dynamic allocation of IPs feature in AKSC has not been implemented inline with our documentation:- https://learn.microsoft.com/en-us/azure/aks/configure-azure-cni-dynamic-ip-allocation. For example, when selecting Dynamic IP as a feature in AKSC, only one subnet (node) is deployed without a pod subnet. In addition, there isn't an option to do BYO vNet and referencing the pod subnet (only an option present for referencing the node subnet). This results in the Subnet IP Usage Workbook[1] not to function correctly due to CNI Dynamic IP allocation implementation not being configured correctly.

[1] https://learn.microsoft.com/en-us/azure/aks/configure-azure-cni#monitor-ip-subnet-usage

Bicep changes implemented:-

• Changes to incorporate the provisioning of a pod subnet when custom vNets is selected.
• BYO AKSPodSubnetId to link an existing pod subnet within an existing vnet.

Helper changes:-

• UI change to introduce a text field to reference the BYO AKSPodSubnetId that shows when Azure CNI Dynamic IP allocation is selected.

PR Checklist

• PR has a meaningful title
• Summarized changes
• This PR is ready to merge and is not Work in Progress
• Link to a filed issue (Customer reported offline, but no issued filed).
• Screenshot of UI changes (if PR includes UI changes)

[Gordonby]

Looks good.
Custom Networking deploys fine

Just a naming issue to tweak