[AVM Module Issue]: `avm/res/container-service/managed-cluster` Add support for Gateway API (`ingressProfile.gatewayAPI`)

Open

#7,101 opened on May 25, 2026 5 comments 0 reactions 1 assignee Claimed by @JPEasier View on GitHub

Class: Resource Module :package: Needs: Immediate Attention :bangbang: Needs: Triage :mag: Status: Response Overdue :triangular_flag_on_post: Type: AVM :a: :v: :m: Type: Feature Request :heavy_plus_sign:

Dominant language: Bicep
Stars: 736
Forks: 564
Avg merge: 3d 15h
Merged PRs (30d): 30

Description

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Issue Type?

Feature Request

### Module Name

avm/res/container-service/managed-cluster

### (Optional) Module Version

0.13.0

### Description

The AKS NGINX Ingress Controller add-on is deprecated. The recommended replacement is the **Kubernetes Gateway API**, now natively supported in AKS via `properties.ingressProfile.gatewayAPI` (stable since API version `2026-03-01`).

The current module does not expose this property. Please add support for configuring Gateway API installation.

### Requested Changes

1. Bump the [managed cluster version](https://learn.microsoft.com/en-us/rest/api/aks/managed-clusters/get?view=rest-aks-2026-03-01&tabs=HTTP) to at least `2026-03-01` or higher.
2. Add a parameter for `ingressProfile.gatewayAPI.installation` (`'Standard'` | `'Disabled'`).
3. Optionally expose `ingressProfile.webAppRouting.gatewayAPIImplementations.appRoutingIstio.mode` for managed Istio-based Gateway API.

### References

- https://learn.microsoft.com/en-us/azure/aks/concepts-network-ingress

### (Optional) Correlation Id

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

[AVM Module Issue]: `avm/res/container-service/managed-cluster` Add support for Gateway API (`ingressProfile.gatewayAPI`)

Description

Contributor guide

Assessment

Get new issues in your inbox