• Ingress NGINX: Statement from the Kubernetes Steering and Security Response Committees In March 2026, Kubernetes will retire Ingress NGINX, a piece of critical infrastructure for about half of cloud native environments.The retirement of Ingress NGINX wasannouncedfor March 2026, after years ofpublic warningsthat the project was in dire need of contributors and maintainers. • There will be no more releases for bug fixes, security patches, or any updates of any kind after the project is retired. • This cannot be ignored, brushed off, or left until the last minute to address. • We cannot overstate the severity of this situation or the importance of beginning migration to alternatives likeGateway APIor one of the manythird-party Ingress controllersimmediately. • To be abundantly clear: choosing to remain with Ingress NGINX after its retirement leaves you and your users vulnerable to attack. • None of the available alternatives are direct drop-in replacements.
Article Summaries:
- In March 2026, the Kubernetes Steering and Security Response Committees announced the retirement of Ingress NGINX, a core component used by roughly half of cloud‑native environments. The project will receive no further releases, bug fixes, or security patches after that date. Committees warned that continued use will expose clusters to attack and urged users to migrate to alternatives such as the Gateway API or other third‑party ingress controllers. Existing deployments will remain functional, but users must verify their reliance on Ingress NGINX within the next two months. The decision follows years of limited maintenance and growing technical debt, underscoring the need for a timely transition.
Sources: