Ingress Nginx: Statement from Kubernetes Steering and Security Committees
5 days ago
- #Ingress NGINX
- #Security
- #Kubernetes
- Kubernetes will retire Ingress NGINX in March 2026 due to lack of contributors and maintainers.
- No further updates, bug fixes, or security patches will be provided post-retirement, posing significant security risks.
- Users are urged to migrate to alternatives like Gateway API or third-party Ingress controllers immediately.
- About 50% of cloud native environments rely on Ingress NGINX, highlighting the widespread impact of this retirement.
- Ingress NGINX has been maintained by only one or two people in their free time in recent years.
- The project's technical debt and design flaws make it unsustainable, even with additional resources.
- Users can check their reliance on Ingress NGINX using a specific kubectl command with cluster admin permissions.
- The Kubernetes Steering and Security Response Committees emphasize the urgency and severity of migrating away from Ingress NGINX.