Kubernetes Ingress Nginx is retiring
9 days ago
- #Gateway API
- #Ingress NGINX
- #Kubernetes
- Kubernetes SIG Network and the Security Response Committee announce the retirement of Ingress NGINX.
- Best-effort maintenance will continue until March 2026, after which no updates or security fixes will be provided.
- Users are recommended to migrate to alternatives like Gateway API or other Ingress controllers listed in Kubernetes documentation.
- Ingress NGINX was an early and popular Ingress controller due to its flexibility and broad feature set.
- Maintenance challenges and insufficient maintainership have led to the decision to retire Ingress NGINX.
- Existing deployments will continue to function, and installation artifacts will remain available post-retirement.
- Users can check if they are using Ingress NGINX with a specific kubectl command.
- The Ingress NGINX maintainers are thanked for their significant contributions to the Kubernetes ecosystem.