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

Kubernetes is retiring Ingress NGINX in March 2026, affecting approximately 50% of cloud native environments and requiring immediate migration planning.

• •Ingress NGINX will receive no further releases, bug fixes, or security patches after retirement in March 2026
• •About 50% of cloud native environments rely on Ingress NGINX, yet it has been maintained by only one or two people in their free time for several years
• •Remaining on Ingress NGINX after retirement exposes users and systems to security vulnerabilities and potential attacks
• •No available alternatives are direct drop-in replacements; migration requires planning and engineering time
• •Users can check if they are affected by running: kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx