To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX. Best-effort maintenance will continue until March 2026. Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered. Existing deployments of Ingress NGINX will continue to function and installation artifacts will remain available.
We recommend migrating to one of the many alternatives.

K8S Contributors

Kubernetes SIG Network and Security Response Committee are retiring Ingress NGINX, one of the most popular Ingress controllers. Best-effort maintenance continues until March 2026, after which no updates, bugfixes, or security patches will be provided. The retirement stems from insufficient maintainership and mounting technical debt. Existing deployments will continue functioning and artifacts remain available, but users are strongly advised to migrate immediately to Gateway API or alternative Ingress controllers. The project's repositories will become read-only for reference.

Ingress NGINX Retirement: What You Need to Know