Kubernetes to Retire Ingress NGINX in March 2026 Due to Security Risks
The Kubernetes Steering and Security Response Committees have announced the official retirement of Ingress NGINX, a critical infrastructure component used by approximately 50% of cloud-native environments, effective March 2026. This decision follows years of insufficient maintenance contributions, with the project recently supported by only one or two volunteers. Post-retirement, no further bug fixes, security patches, or updates will be released, leaving existing deployments vulnerable to cyberattacks. The committees emphasize that this is not a drop-in replacement scenario; migration requires significant engineering planning and time. Users are urged to immediately verify their reliance on Ingress NGINX using specific kubectl commands and begin transitioning to alternatives such as the Gateway API or third-party ingress controllers. The retirement is driven by accumulated technical debt and fundamental design flaws that exacerbate security issues, making continued maintenance unfeasible. With only two months remaining before the deadline, the statement warns that ignoring this change poses severe risks to user safety and ecosystem stability. The move aims to refocus community efforts on more modern, secure networking solutions within the Kubernetes ecosystem.
Wire timeline
Kubernetes to Retire Ingress NGINX in March 2026 Due to Security Risks
The Kubernetes Steering and Security Response Committees have announced the official retirement of Ingress NGINX, a critical infrastructure component used by approximately 50% of cloud-native environments, effective March 2026. This decision follows years of insufficient maintenance contributions, with the project recently supported by only one or two volunteers. Post-retirement, no further bug fixes, security patches, or updates will be released, leaving existing deployments vulnerable to cyberattacks. The committees emphasize that this is not a drop-in replacement scenario; migration requires significant engineering planning and time. Users are urged to immediately verify their reliance on Ingress NGINX using specific kubectl commands and begin transitioning to alternatives such as the Gateway API or third-party ingress controllers. The retirement is driven by accumulated technical debt and fundamental design flaws that exacerbate security issues, making continued maintenance unfeasible. With only two months remaining before the deadline, the statement warns that ignoring this change poses severe risks to user safety and ecosystem stability. The move aims to refocus community efforts on more modern, secure networking solutions within the Kubernetes ecosystem.
Kubernetes Blog