Ingress NGINX Retirement: Impact, Risks, and Migration Strategies

Background

The Kubernetes Steering Committee and Security Response Committee announced that the Ingress NGINX controller will be retired. Maintenance will continue only until March 2026, after which no new releases, vulnerability fixes, or security patches will be provided. The GitHub repository will be set to read‑only, and existing deployments will keep running, but users must migrate to alternative solutions.

Official Announcements

English announcement: https://kubernetes.io/blog/2026/01/29/ingress-nginx-statement/

Key points from the announcement:

Support ends in March 2026.

Approximately 50 % of cloud‑native environments rely on Ingress NGINX.

Continuing to use the controller after end‑of‑life exposes clusters to security risks.

Migration to Gateway API or other third‑party ingress controllers is required.

How to Check If You Are Affected

Run the following command to list any Ingress NGINX pods in the cluster:

kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx

Reasons for Retirement

Ingress NGINX suffers from chronic understaffing. Internal research shows that while about half of cloud‑native workloads depend on it, only one or two maintainers work on the project in their spare time. Accumulated technical debt and design flaws have created ongoing security liabilities, making continued maintenance untenable.

Migration Guidance

Users are encouraged to migrate to alternative ingress solutions such as the Gateway API or the Higress API Gateway. Relevant migration resources include:

Migration guide from Ingress NGINX to Higress Enterprise (API Gateway): https://help.aliyun.com/zh/api-gateway/cloud-native-api-gateway/user-guide/migrating-from-nginx-ingress-to-cloud-native-api-gateway

Open‑source migration instructions for Higress: https://higress.cn/docs/latest/user/annotation/