Kubernetes has announced that it will officially retire the popular Ingress NGINX controller in March 2026. Despite being critical to approximately 50% of cloud native environments, the project faces persistent maintainer shortages and significant security vulnerabilities. This decision is driven by the need to ensure a more secure and maintainable ingress solution for users.
The challenges with Ingress NGINX have been mounting, with critical vulnerabilities like the IngressNightmare set carrying a CVSS score of 9.8, and recent findings of four new vulnerabilities, including CVE-2026-1580 and CVE-2026-24512, affecting older versions. The latter, with a CVSS score of 8.8, allows configuration injection and arbitrary code execution.
The Kubernetes Steering and Security Response Committees have warned that post-March 2026, there will be no further updates, bug fixes, or security patches available for Ingress NGINX. Users must proactively plan to migrate to more secure alternatives such as the Gateway API or other third-party Ingress controllers. The Gateway API offers a modern, standardized, and actively maintained successor, designed to separate concerns across infrastructure and applications, providing enhanced security and extensibility.
This transition is critical as remaining with Ingress NGINX post-retirement drastically increases security risks. Kubernetes recommends users audit their deployments using tools like the ingress2gateway automation tool, which facilitates the migration by mapping annotations to HTTPRoute logic, and allows for learning new objects inherent to the Gateway API.
For those unable to migrate immediately, Chainguard has stepped in with its EmeritOSS program, offering continued support beyond the retirement deadline. However, in anticipation of unsupported deployments, Kubernetes emphasizes the urgency of migration planning to prevent potential security issues.
This Ingress NGINX retirement is part of broader developments in the cloud native ecosystem, including the archiving of the Kubernetes Dashboard and the formation of a new Checkpoint/Restore Working Group. As the ecosystem evolves, users are encouraged to stay informed through community updates, security advisories, and tutorials, and to participate in upcoming KubeCon events to better navigate these changes.

Collections

Kubernetes will retire the Ingress NGINX controller in March 2026 due to maintainer shortages and critical security vulnerabilities (including CVE-2026-1580 with CVSS 8.8). After retirement, no updates or patches will be available. Users must migrate to alternatives like the Gateway API, which offers better security and maintainability. Migration tools like ingress2gateway are available to assist. Chainguard's EmeritOSS program provides extended support for those unable to migrate immediately.

The Impending Retirement of Ingress NGINX and Its Impact on Cloud Native Environments