Ingress NGINX · Lifecycle Status

Ingress NGINX End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Ingress NGINX versions. Dates read at the vendor's own lifecycle pages (kubernetes.io). Updated at every deploy.

⚠ All Ingress NGINX versions are past end of life. No security patches are being issued. Migrate to a supported alternative or purchase extended support.

Every tracked Ingress NGINX version is past end of life; the most recent to reach it, 1, did so in March 2026. The full Ingress NGINX lifecycle, with every version's release and end-of-support date, is in the table below.

Running an EOL version? Get matched with support options — free ↓
Latest Active
—
— series
Next EOL
—
None upcoming
Active Versions
0
of 1 total
EOL Versions
1
no longer patched
40 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
30/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
CPE Identifier
cpe:2.3:a:kubernetes:ingress-nginx
The Common Platform Enumeration name vulnerability scanners and CVE records use for Ingress NGINX. Verified against the NIST CPE dictionary. Machine-readable for all products: cpe-map.json
Package URLs (purl)
pkg:github/kubernetes/ingress-nginx
pkg:golang/k8s.io/ingress-nginx
The package URL identifiers SBOM tools emit for Ingress NGINX, so a CycloneDX or SPDX component resolves to this page by exact identifier rather than by name. Machine-readable for all products: purl-map.json; whole-SBOM checks: POST /v1/sbom or the Stack Scanner.
Release Cycle Timeline
■ EOL   ■ Warning   ■ Active   ┊ Today
Release cycle timeline 2022202320242025202620271TODAY
1 version of Ingress NGINX is past end of life — security patches have stopped. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1 1.15.1 Aug 24, 2021 Mar 2026 EOL since March 2026 EOL
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Ingress NGINX EOL status badge Live EOL badge for your README — updates automatically at every build. [![Ingress NGINX EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fingress-nginx.json)](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. In the project's words, after retirement there are no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered, in a component that by design sits on the cluster edge parsing untrusted traffic. This page is about the community controller, kubernetes/ingress-nginx; NGINX Ingress Controller from F5 is a separate product and is not retired.

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 carries any newly found vulnerability at its most exposed point with no fix coming from the project, which is why the Kubernetes project tells users to migrate.

What does Ingress NGINX end of life mean for your organization?

When a version of Ingress NGINX reaches end of life, the vendor's standard security patches for that version stop. Vulnerabilities found after that date are still published on the National Vulnerability Database, exploit code often becomes public, and systems on that version stay exposed until they are upgraded or covered by extended support.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but the vendor's policy provides no patch for the ended version. This is one of the most dangerous gaps 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.

OptionBest whenWatch 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, check whether the vendor or a third party sells extended support with security patches for your Ingress NGINX version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get Ingress NGINX Support Options

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."

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for Ingress NGINX?
See the full table above for all Ingress NGINX version EOL dates.
When is the Ingress NGINX support end date?
Each Ingress NGINX version has its own support end date — see the table above for every version's date.
What is the latest supported version of Ingress NGINX?
No Ingress NGINX version is currently supported: every version we track is past end of life. The table above has each version's end date.
What happens when Ingress NGINX reaches end of life?
When Ingress NGINX reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor patch path — a growing attack surface that a CVE-based scan does not show. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give the date in advance.
How do I check if I'm running an EOL version of Ingress NGINX?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Ingress NGINX versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.
Deep Dive
Full guide
Ingress NGINX (ingress-nginx) End of Life: Retired March 2026
→

Related Products

✓ 2 of 2 lifecycle dates vendor-sourced · confidence: 0 high, 2 medium, 0 low (each version page shows where every date comes from) · provenance · Source: the vendor's own lifecycle pages (kubernetes.io) · Generated at build time · How we source data →
Ingress NGINX end-of-life status badge