Kubernetes

1259 readers

2 users here now

founded 2 years ago

MODERATORS

erlingur@programming.dev

Daemon@programming.dev

Ingress NGINX: Statement from the Kubernetes Steering and Security Response Committees (kubernetes.io)

submitted 3 days ago* (last edited 2 days ago) by nemeski@mander.xyz to c/kubernetes@programming.dev

2 comments fedilink hide all child comments

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.

top 2 comments

sorted by: hot top controversial new old

[–] higgsboson@piefed.social 2 points 3 days ago

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

[–] towerful@programming.dev 1 points 2 days ago* (last edited 2 days ago)

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