<p>The Kubernetes SIG Network and Security Response Committee has announced the retirement of Ingress NGINX, a widely used Ingress controller within the Kubernetes ecosystem. This decision arises from significant maintenance challenges and security vulnerabilities that have become insurmountable despite the solution’s popularity.</p>
<h3>Reasons for Retirement</h3>
<p>The retirement, set to complete by March 2026, primarily stems from insufficient maintainership and escalating technical debt. Over the years, Ingress NGINX accrued a backlog of legacy features, which have evolved into notable security liabilities. Moreover, a lack of dedicated developer resources—often with only one or two contributors working in their free time—exacerbated these issues, leaving the project vulnerable to security threats. In 2025 alone, multiple critical vulnerabilities were discovered, including flaws that posed a significant risk of enabling complete cluster control takeovers.</p>
<h3>Maintenance Timeline and Recommendations</h3>
<p>Ingress NGINX will receive best-effort maintenance until March 2026, with no further updates, bug fixes, or security patches provided post this period. Existing deployments will continue to function as normal, and project artifacts will remain accessible. Nonetheless, to mitigate risks, users are advised to start planning migrations immediately. Options include transitioning to the Gateway API or using alternative Ingress controllers.</p>
<h3>Planning for Migration</h3>
<p>With approximately 6,000 implementations currently relying on Ingress NGINX, administrators face the urgent task of developing new strategies to ensure continued security and functionality. The project’s repositories will be set to read-only status, serving as a reference for the community, as stakeholders navigate the transition phase.</p>
<p>This strategic shift serves as a pivotal moment for Kubernetes users, prompting a reassessment of current implementations in favor of more sustainable and secure options moving forward.</p>


Collections

Kubernetes SIG Network and Security Response Committee is retiring Ingress NGINX by March 2026 due to insufficient maintainership, technical debt, and critical security vulnerabilities. The project will receive best-effort maintenance until the deadline, after which no updates or patches will be provided. With approximately 6,000 implementations affected, users should begin planning migrations to alternatives like the Gateway API or other Ingress controllers to maintain security and functionality.

Understanding the Retirement of Ingress NGINX