Ingress NGINX End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Ingress NGINX versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.15.1 | Aug 24, 2021 | Mar 31, 2026 | 145 days past EOL | EOL |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/ingress-nginx)
Ingress NGINX lifecycle status — the real story
Ingress NGINX is one of the most consequential end-of-life events in modern infrastructure: the Kubernetes project officially retired it in March 2026, announced November 11, 2025 by SIG Network and the Security Response Committee. After the final release (1.15.1, March 2026) there will be no further releases, no bug fixes, and — critically — no fixes for any security vulnerability ever discovered again, in a component that by design sits on the cluster edge parsing untrusted traffic.
The retirement wasn't sudden decay: the project ran for years on one or two volunteer maintainers, and its famous flexibility (arbitrary NGINX directives via "snippets" annotations) turned into unfixable attack surface — the IngressNightmare vulnerability cluster of March 2025 was the loudest warning. Kubernetes' official guidance is to migrate to the Gateway API or another maintained ingress controller immediately.
The scale of the problem is the story: ingress-nginx was the default ingress for a huge share of production Kubernetes clusters, and migrations of edge routing are slow, risky projects. Every cluster still running it past March 2026 is accumulating permanently unpatchable CVEs at its most exposed point — which is why commercial extended support for it appeared almost immediately.
What does Ingress NGINX end of life mean for your organization?
When a version of Ingress NGINX reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Ingress NGINX should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Ingress NGINX reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Ingress NGINX versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Ingress NGINX has 1 version past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Ingress NGINX exists — vetted vendors ship security patches for years past the official date. Right now that coverage spans Ingress NGINX 1.15.1, with 60+ post-EOL CVE fixes documented in vendor release notes. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."