[AVM Module Issue]: 0.5.1 incompatible with BYO vnet PodSubnetID container-service/managed-cluster

[KLuuKer]

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.5.1

Description

0.5.1 ❌ introduced a braking change when used with BYO vnet "PodSubnetID"
0.5.0 ✅ worked fine previously

primaryAgentPoolProfiles: [
  {
    vnetSubnetResourceId: aksSystemNodeSubnet.id
    podSubnetResourceId: aksSystemPodSubnet.id
    // other config omitted..
  }
]
agentPools: [
  {
    vnetSubnetResourceId: aksUserNodeSubnet.id
    podSubnetResourceId: aksUserPodSubnet.id
    // other config omitted..
  }
]

networkDataplane: 'cilium'
networkPlugin: 'azure'
networkPluginMode: null

which results with the following error:

Preflight validation check for resource(s) for container service myakscluster in resource group myresourcegroup failed.
Message: NetworkPluginMode overlay cannot be used with PodSubnetID.
Details: (Code: BadRequest)

(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]

@KLuuKer, 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!

[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)!

[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)!

[microsoft-github-policy-service]

Caution

**This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-bicep) immediate attention as it hasn't been responded to within 6 business days. **

Tip

• To avoid this rule being (re)triggered, the "Needs: Triage 🔍" and "Status: Response Overdue 🚩" labels must be removed when the issue is first responded to!
• Remove the "Needs: Immediate Attention ‼️" label once the issue has been responded to.

[KLuuKer]

@JPEasier i can't update to any new version unless this issue is resolved

[JPEasier]

Hi @KLuuKer, Thanks for pointing out.

Unfortunately, we are currently experiencing a blocking issue in the AKS module that needs to be resolved before I can address it here. I ask for your patience.

thank you!