[AVM Module Issue]: Support API Server VNet Integration in `container-service/managed-cluster`

[coolhome]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

Module Name

avm/res/container-service/managed-cluster

(Optional) Module Version

No response

Description

https://learn.microsoft.com/en-us/azure/aks/api-server-vnet-integration

Below is what I've been using locally and it's been working pretty well 🧑‍🚒

@description('Optional. Enable API Server vnet integration. Requires subscription feature flag `EnableAPIServerVnetIntegrationPreview` to be enabled during preview.')
param enableApiServerVnetIntegration bool = false

@description('Optional.  API Server subnet resource id.')
param apiServerSubnetResourceId string?

    apiServerAccessProfile: {
      authorizedIPRanges: authorizedIPRanges
      disableRunCommand: disableRunCommand
      enablePrivateCluster: enablePrivateCluster
      enablePrivateClusterPublicFQDN: enablePrivateClusterPublicFQDN
      privateDNSZone: privateDNSZone
      
      // START MOD
      enableVnetIntegration: enableApiServerVnetIntegration
      subnetId: apiServerSubnetResourceId
      // END MOD
    }

(Optional) Correlation Id

No response

[avm-organizer]

@coolhome, 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 team will review it soon!

[PixelRobots]

I think we should add this once the feature has gone GA, which will hopefully happen soon.

I also think we should add a new test deployment for this too.

[AlexanderSehr]

I think we should add this once the feature has gone GA, which will hopefully happen soon.

I also think we should add a new test deployment for this too.

I'd argee and it would also align with the repository's specs. It's technically not forbidden - but not encouraged 😉 @JPEasier, what's your take?

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

Note

This message was posted as per ITA01BCP.

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

Note

This message was posted as per ITA02BCP.

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

Note

This message was posted as per ITA01BCP.