Ingress NGINX: Statement from the Kubernetes Steering and Security Response Committees

Syndicated from the fediverse. Read and engage on the original instance.

Ingress NGINX: Statement from the Kubernetes Steering and Security Response Committees

In March 2026, Kubernetes will retire Ingress NGINX, a piece of critical infrastructure for about half of cloud native environments. The retirement of Ingress NGINX was announced for March 2026, after years of public warnings that the project was in dire need of contributors and maintainers. There will be no more releases for bug fixes, security patches, or any updates of any kind after the project is retired. This cannot be ignored, brushed off, or left until the last minute to address.

https://kubernetes.io/blog/2026/01/29/ingress-nginx-statement/Open link View original on mander.xyz

Comments3

3 replies

towerful

programming.dev

The retirement of Ingress NGINX was announced for March 2026, after years of public warnings that the project was in dire need of contributors and maintainers. There will be no more releases for bug fixes, security patches, or any updates of any kind after the project is retired.
This cannot be ignored, brushed off, or left until the last minute to address. We cannot overstate the severity of this situation or the importance of beginning migration to alternatives like Gateway API or one of the many third-party Ingress controllers immediately.

I know it's literally the first paragraph, but I thought it worth commenting for those that only read the title & comments

sherlockhomelessok

lemmy.world

We use nginx-ingress-controller alongside another opt-in, paid solution. Very sad to see that this is how orgs are thinking about open source. Thousands of people are profiting from the foundational work of a few.

higgsboson

piefed.social

ingress-nginx was an Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer.