kubernetes node feature discovery end of life dates — full support timeline
6 of 8 tracked kubernetes node feature discovery releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 0.19 | 2026-07-10 | not announced | 0.19.0 | supported |
| 0.18 | 2025-10-02 | not announced | 0.18.3 | supported |
| 0.17 | 2024-12-22 | 2026-07-10 | 0.17.4 | ended |
| 0.16 | 2024-05-27 | 2025-10-02 | 0.16.9 | ended |
| 0.15 | 2023-08-08 | 2024-12-24 | 0.15.7 | ended |
| 0.14 | 2023-04-19 | 2024-05-27 | 0.14.6 | ended |
| 0.13 | 2022-12-21 | 2023-04-19 | 0.13.6 | ended |
| 0.12 | 2022-06-07 | 2023-09-12 | 0.12.5 | ended |
Who is affected
Anyone running an unsupported kubernetes node feature discovery release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/kubernetes-node-feature-discovery, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next kubernetes node feature discovery deadline
You are reading this because a kubernetes node feature discovery release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every kubernetes node feature discovery and related deadline as it is announced, with exact dates and primary sources.
Watch kubernetes node feature discovery deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.