Kubernetes Node Feature Discovery · Lifecycle Status

Kubernetes Node Feature Discovery End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Kubernetes Node Feature Discovery versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Kubernetes Node Feature Discovery 0.17.4 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
0.17.4
0.17 series
Next EOL
None upcoming
Active Versions
2
of 7 total
EOL Versions
5
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20232024202520260.120.130.140.150.160.170.18TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
0.12 0.12.5 Jun 7, 2022 Sep 12, 2023 970 days past EOL EOL
0.13 0.13.6 Dec 21, 2022 Apr 19, 2023 1116 days past EOL EOL
0.14 0.14.6 Apr 19, 2023 May 27, 2024 712 days past EOL EOL
0.15 0.15.7 Aug 8, 2023 Dec 24, 2024 501 days past EOL EOL
0.16 0.16.9 May 27, 2024 Oct 2, 2025 219 days past EOL EOL
0.17 0.17.4 Dec 22, 2024 Already EOL Supported Active
0.18 0.18.3 Oct 2, 2025 Already EOL Supported Active

What does Kubernetes Node Feature Discovery end of life mean for your organization?

When a Kubernetes Node Feature Discovery version 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 Kubernetes Node Feature Discovery 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Kubernetes Node Feature Discovery?
See the full table above for all Kubernetes Node Feature Discovery version EOL dates.
What is the latest supported version of Kubernetes Node Feature Discovery?
The latest active version of Kubernetes Node Feature Discovery is 0.17.4. Always verify against the table above as support windows can change.
What happens when Kubernetes Node Feature Discovery reaches end of life?
When Kubernetes Node Feature Discovery reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Kubernetes Node Feature Discovery?
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 Kubernetes Node Feature Discovery versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →