Kubernetes Node Feature Discovery End of Life Dates
other
Developers working with Kubernetes rely on tools like Kubernetes Node Feature Discovery to streamline their workflow and optimize resource utilization. Created to simplify the process of discovering node features in Kubernetes clusters, this project has been maintained by the Kubernetes community since its inception. The goal of Kubernetes Node Feature Discovery is to provide a standardized way of detecting node capabilities, making it easier for developers to manage and deploy applications on Kubernetes. By keeping track of end-of-life dates and supported versions, developers can ensure their applications remain secure and up-to-date.
The end-of-life landscape for Kubernetes Node Feature Discovery is characterized by a total of 7 versions, with 5 of these versions having already reached their end-of-life. Currently, 2 versions remain active, with the latest stable version being 0.18.3. Notably, the last end-of-life date occurred on 2025-10-02, affecting version 0.16. Since there is no next scheduled end-of-life date, developers can continue to use the current active versions without immediate concern for upcoming support deadlines. This information is crucial for planning upgrades and migrations, allowing developers to proactively manage their dependencies and minimize potential disruptions.
From a security perspective, Kubernetes Node Feature Discovery has a spotless record, with 0 tracked CVEs and 0 critical vulnerabilities. As a result, there is no most affected version, and no known exploits pose an immediate threat to applications using this tool. Furthermore, with no recorded security issues, Kubernetes Node Feature Discovery does not have a KEV status. Given this favorable security posture, developers can confidently continue to use and integrate Kubernetes Node Feature Discovery into their projects, focusing on other aspects of security and maintenance. Regularly reviewing the project's status and updates will remain essential for ensuring the long-term security and stability of their applications.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 0.18 | Oct 2, 2025 | — | No | — | 0.18.3 | — | Active | |
| 0.17 | Dec 22, 2024 | — | No | — | 0.17.4 | — | Active | |
| 0.16 | May 27, 2024 | — | Oct 2, 2025 | 295d ago | 0.16.9 | — | EOL | |
| 0.15 | Aug 8, 2023 | — | Dec 24, 2024 | 577d ago | 0.15.7 | — | EOL | |
| 0.14 | Apr 19, 2023 | — | May 27, 2024 | 788d ago | 0.14.6 | — | EOL | |
| 0.13 | Dec 21, 2022 | — | Apr 19, 2023 | 1192d ago | 0.13.6 | — | EOL | |
| 0.12 | Jun 7, 2022 | — | Sep 12, 2023 | 1046d ago | 0.12.5 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
