Kubernetes Node Feature Discovery Lifecycle policy

Kubernetes Node Feature Discovery is tracked by BlackTree as a server-side software product. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Evidence status

This record passed BlackTree's automatic primary-source checks with a confidence score of 82. It is returned for operational research without requiring routine manual approval. Confirm edition and deployment applicability before acting.

This discovery does not establish a product-specific support or retirement date. A missing date does not mean support continues.

Product overview

Main capabilities

Networked or application service delivery
Administrative and operational interfaces
Versioned maintenance and security updates

Typical use

Used to provide application, infrastructure or operational services to other systems and users.

Deployment

Deployed on servers, virtual machines, containers or managed infrastructure.

This category-level context is generated from the registered product identity. Confirm exact product capabilities on the publisher's page .

Collected lifecycle data

Product	Kubernetes Node Feature Discovery
Release	Lifecycle policy
Start or release	Not extracted
Lifecycle boundary	Continuous or not dated in the source
Date precision	Unknown

Known exploited vulnerabilities

Catalogue updated 31 Oct 2026

These are product-family matches in the CISA Known Exploited Vulnerabilities catalogue. Confirm the affected product version in the vendor advisory.

No CISA known-exploited entries currently match this mapped product family.

This does not mean the product has no vulnerabilities.

Package vulnerability advisories

Checked 2 Nov 2026

OSV advisories are matched through the registered package URL. A package-family match does not prove that the installed release is affected. Check the affected and fixed versions before remediation.

No package advisories have been linked for this product identity.

This is not evidence that the product has no vulnerabilities.

Source evidence

PRIMARYManual

Kubernetes Node Feature Discovery official lifecycle source

Helm: set metadata.namespace on the PodMonitor. When the chart is rendered through Kustomize's Helm integration (Kustomize 5.8 and later), the PodMonitor had no namespace and Argo CD refused to sync it with InvalidSpecError: Namespace for ... PodMonitor is missing ( #2577 , fixes #2576 ). | Helm: render priorityClassName once in the nfd-worker pod spec. With both the top-level priorityClassName and worker.priorityClassName set, the key was emitted twice and the effective value depended on the YAML decoder; worker.priorityClassName now takes precedence and falls back to the top-level value. The nfd-gc container securityContext is now configurable with gc.securityContext , which defaults to the previously hardcoded settings ( #2624 , fixes #2622 ). | kustomize: the prune overlay works again. It removed /rules/1 from the nfd-master ClusterRole with a JSON patch, and since v0.17.0 that index is the nodes rule, so the prune Job failed with nodes is forbidden: ... cannot list resource "nodes" and left all NFD labels, annotations and extended resources on the nodes ( #2607 ). | nfd-master: NodeFeatureGroup status lists member nodes by Node name. It used the system.name feature's nodename element, so nodes whose features came only from third-party NodeFeature objects were listed with an empty name ( #2621 ). | nfd-master: NodeFeatureGroups outside nfd-master's own namespace get their status populated. The update queue was keyed by object name only, so same-name NodeFeatureGroups in different namespaces collided, and the lookup and status write were pinned to nfd-master's namespace ( #2559 ).

Publisher identity used by product-specific official-source collectors.

First collected 12 Sep 2026 · Last collected 1 Nov 2026 · Review state accepted

Open official vendor source