# ingress nginx retirement

The retirement of Ingress NGINX, a Kubernetes Ingress controller that used NGINX as a reverse proxy and load balancer.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Ingress NGINX Retirement: What You Need to Know

DevFeed: [Ingress NGINX Retirement: What You Need to Know](<https://devfeed.tech/articles/ingress-nginx-retirement-what-you-need-to-know-17593.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2025/11/12/ingress-nginx-retirement/>)

Author: The Kubernetes Authors

Published: 2025-11-12T17:00:00Z

Content type: release

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [ingress-nginx](<https://devfeed.tech/topics/ingress-nginx.md>), [ingress nginx retirement](<https://devfeed.tech/topics/ingress-nginx-retirement.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Security](<https://devfeed.tech/topics/security.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [alternatives](<https://devfeed.tech/tags/alternatives.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [ingress-nginx](<https://devfeed.tech/tags/ingress-nginx.md>), [ingress-nginx-retirement](<https://devfeed.tech/tags/ingress-nginx-retirement.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [releases](<https://devfeed.tech/tags/releases.md>), [security](<https://devfeed.tech/tags/security.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>)

### AI overview

Kubernetes SIG Network and the Security Response Committee announce the upcoming retirement of Ingress NGINX. Best-effort maintenance will continue until March 2026; afterward, the project will receive no further releases, bug fixes, or security updates. Existing deployments and installation artifacts will remain available, and users are encouraged to migrate to alternatives such as Gateway API.

### Source excerpt

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. Consider migrating to Gateway API , the modern replacement for Ingress. If you must continue using Ingress, many alternative Ingress controllers are listed in the Kubernetes documentation . Continue reading for further information about the history and current state of Ingress NGINX, as well as next steps. About Ingress NGINX Ingress is the original user-friendly way to direct network traffic to workloads running on Kubernetes. (Gateway API is a newer way to achieve many of the same goals.) In order for an Ingress to work in your cluster, there must be an Ingress controller running. There are many Ingress controller choices available, which serve the needs of different users and use cases. Some are cloud-provider specific, while others have more general applicability. Ingress NGINX was an Ingress controller, developed early in the history of the Kubernetes project as an example implementation of the API. It became very popular due to its tremendous flexibility, breadth of features, and independence from any particular cloud or infrastructure provider. Since those days, many other Ingress controllers have been created within the Kubernetes project by community groups, and by cloud native vendors. Ingress NGINX has continued to be one of the most popular, deployed as part of many hosted Kubernetes platforms and within innumerable independent users' clusters. History and Challenges The breadth and flexibility of Ingress NGINX has caused maint