Node Feature Discovery

Node Feature Discovery (NFD) is a Kubernetes add-on for detecting hardware features and system configuration.

  • Infrastructure
  • Tools & Utilities
Node Feature Discovery (NFD) is a Kubernetes add-on for detecting hardware features and system configuration. Detected features are advertised as node labels. NFD provides flexible configuration and extension points for a wide range of vendor and application specific node labeling needs.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

74/100 Good

Maintained
100last commit 14 days ago
Popular
611,089 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
87no serious findings, CI, tests, OpenSSF Scorecard 6.7/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
1,089
Open issues
42
Last commit
2026-11-06
Latest release
v0.20.1
License
Apache-2.0
Activity
declining

Checked 14 days ago - source: GitHub (kubernetes-sigs/node-feature-discovery)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Use the default Helm install first Run the default Helm install and let it create the node-feature-discovery namespace. This keeps NFD's pods and labels in their own space, so they do not clash with other workloads. source
  • Put custom labels in the right folders If you want extra labels, put plain-text feature files in /etc/kubernetes/node-feature-discovery/features.d/ and matching YAML (simple text config) rules in custom.d/. NFD only looks in those folders, so files saved somewhere else will be ignored. source
  • Try the sample custom-rules overlay Apply the custom-rules overlay if you want a working example, such as a label for a loaded kernel module. Without a rule file, NFD will not create custom labels from conditions you define. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What K3s network issue has been reported when running Node Feature Discovery?

A k3s user reported that the default CNI may not allow communication between the master and worker nodes.

How does nfd-worker handle node labels across repeated runs?

Consecutive runs update the labels on a node. If a feature is not discovered on a later run, its label is removed. This applies even with restrictions such as a label whitelist.

What production failure pattern is called out for Node Feature Discovery?

One recurring pattern is feature label inconsistency after a node restart.

Where can a Node Feature Discovery usage demo be found?

The examples page points to a demo in the source code repository under the demo directory.

Answers sourced from github.com, kubernetes-sigs.github.io, perun.au, www.reddit.com

Community

Collected 48 days ago - public community threads