TL;DR

Ingress NGINX will be retired by Kubernetes SIG Network and Security Response Committee due to maintenance challenges. Users are advised to migrate to Gateway API or alternative Ingress controllers by March 2026.

What happened

Kubernetes SIG Network and the Security Response Committee have announced the retirement of Ingress NGINX, a popular Ingress controller. Maintenance will cease in March 2026, with no further releases or security updates post-retirement.

Why it matters for ops

Ingress NGINX faces significant technical debt and maintenance challenges due to its breadth and flexibility. The Kubernetes community aims to prioritize user safety by transitioning users to more sustainable solutions like Gateway API.

Action items

  • Migrate from Ingress NGINX to Gateway API or another supported controller
  • Review Kubernetes documentation for alternative Ingress controllers
  • Verify current deployment status with 'kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx'

Source link

https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/