TL;DR

Kubernetes is set to retire Ingress NGINX in March 2026 due to lack of maintainers and security concerns. Half of all Kubernetes users rely on Ingress NGINX, necessitating an urgent migration to secure alternatives.

What happened

The Kubernetes Steering and Security Response Committees announced the retirement of Ingress NGINX in March 2026, urging immediate action for those using this infrastructure due to critical security risks. The project lacks sufficient maintainers, leading to potential vulnerabilities.

Why it matters for ops

Ops teams must address this issue promptly because ignoring it exposes their systems and users to significant security threats. Ingress NGINX will no longer receive updates or patches after retirement.

Action items

  • Evaluate current use of Ingress NGINX with commands like `kubectl get pods`
  • Begin planning migration to alternatives such as Gateway API or other Ingress controllers
  • Implement security measures to mitigate risks before the deadline

Source link

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