Skip to main content

Update on the Azure Kubernetes Service (AKS) Application Routing add-on, the Ingress API, and Ingress-NGINX

· 2 min read
Ahmed Sabbour
Ahmed Sabbour
Principal PM Lead for the Azure Kubernetes Service

The Kubernetes SIG Network and the Security Response Committee have announced the upcoming retirement of the Ingress NGINX project, with maintenance ending in March 2026.

No immediate action required​

Microsoft understands that customers value continuity and clarity around the maintenance and evolution of the components that power their workloads. There is no change or immediate action required today for AKS clusters using the Application Routing add-on with NGINX to manage Ingress NGINX resources. Microsoft will provide official support for Application Routing add-on Ingress NGINX resources through November 2026 and only for critical security patches during this period.

We are actively investing in the future of application connectivity in Azure Kubernetes Service (AKS), centered on the Gateway API. This includes support for the Gateway API in the Istio-based service mesh add-on, expanding the Application Routing add-on to support the Gateway API, and continuing investment in Application Gateway for Containers.

The future of the Application Routing add-on​

Application Routing with Gateway API, which will be powered by the Istio control plane for Gateway API-based ingress only, is planned for the first half of 2026, along with migration guidance documentation. The Kubernetes Gateway API represents the next generation of Kubernetes ingress traffic management, evolving from the Ingress API by offering richer routing capabilities, standardized extensibility, and a more secure, role-oriented design.

Alternative migration paths​

Alternatively, existing users of Ingress NGINX, including users who provisioned it through Application Routing add-on, can also migrate to one of the following options:

For further questions, you can reach us on GitHub or create a support case.