Chainguard Container for node-feature-discovery

A minimal wolfi-based image for node-feature-discovery, Node feature discovery for Kubernetes

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/node-feature-discovery:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

Chainguard's node-feature-discovery container image is comparable to the official upstream Node Feature Discovery (NFD) image. Like other Chaingaurd Containers, node-feature-discovery was designed with minimalism in mind, and does not include tools such as a shell or package manager.

node-feature-discovery also has the following differences from the upstream image:

• Paths and Configuration: The image expects the NFD worker configuration file to be located at /etc/kubernetes/node-feature-discovery/nfd-worker.conf by default. You may need to map custom paths depending on your environment.
• Compatibility with gRPC: The Chainguard NFD image is designed with modern Kubernetes APIs in mind, so it might not support older, deprecated gRPC configurations that are available in upstream images. This aligns with best practices in Kubernetes, but may be a consideration for legacy systems.

Getting Started

node-feature-discovery can be deployed using the upstream Helm chart. Note that you will need to override the default image and tag used, replacing them with the Chainguard image, as with the following example values.yaml file:

image:
  repository: cgr.dev/ORGANIZATION/node-feature-discovery
  tag: latest

Use this values file to deploy node-feature-discovery:

helm repo add node-feature-discovery https://kubernetes-sigs.github.io/node-feature-discovery/charts
helm repo update

export NFD_NS=node-feature-discovery
helm install node-feature-discovery node-feature-discovery/node-feature-discovery \
  --namespace $NFD_NS --create-namespace \
  -f values.yaml

Refer to the Helm chart documentation for full instructions on how to use the Helm chart.

NFD is recommended to be run in a Linux environment for seamless integration. While it is possible to run this on macOS, additional configuration may be required (such as handling file system mounts and port exposure) due to Docker running inside a VM.

You can apply NFD resources using kubectl:

kubectl apply -k "https://github.com/kubernetes-sigs/node-feature-discovery/deployment/overlays/default?ref=master"

You can also check the status of pods:

kubectl -n node-feature-discovery get all

NAME                              READY   STATUS    RESTARTS   AGE
pod/nfd-gc-565fc85d9b-94jpj       1/1     Running   0          18s
pod/nfd-master-6796d89d7b-qccrq   1/1     Running   0          18s
pod/nfd-worker-nwdp6              1/1     Running   0          18s
...

Documentation and Resources

• Node Feature Discovery Documentation
• Node Feature Discovery GitHub Repository

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.