Release v0.4.0

[marquiz]

Release checklist:

• All OWNERS must LGTM the release proposal.
• Update the daemonset template and the job template to use the new tagged container image
• An OWNER runs git tag -s $VERSION and insert the changelog into the tag description.
• Build and push a container image with the same tag to quay.io.
• Update the :latest virtual tag in quay.io to track the last stable (this) release.
• An OWNER pushes the tag with git push $VERSION.
• Write the change log into the Github release info.
• Add a link to the tagged release in this issue.
• An announcement email is sent to kubernetes-dev@googlegroups.com with the
  subject [ANNOUNCE] node-feature-discovery $VERSION is released
• Close this issue.

Changelog

Node-feature-discovery was migrated into a new repository under the kubernetes-sigs organization in Github (#175). Related to the migration, the final container image registry/repo hasn't been dediced yet (#177) – for this release we still use the old repo.

Major changes

• Split NFD into client and server (Split NFD into client and server #209)
• Changes in labels:
  • NFD label namespace was changed to feature.node.kubernetes.io/ (Change node label name(space) #176)
    • nfd- prefix was dropped from all feature labels
    • NFD version label (feature.node.kubernetes.io/node-feature-discovery.version) was replaced by an annotation (nfd.node.kubernetes.io/version)
  • network SRIOV labels were changed (network: rename sriov labels #173):
    • network-sriov -> network-sriov.capable
    • network-sriov-configured -> network-sriov.configured
  • selinux detection was moved to kernel feature source
    • selinux -> kernel-selinux.enabled
  • cpuid, pstate and RDT labels moved under cpu feature source (sources: move all cpu related features under the cpu source #217)
    • cpuid-<cpuid flag> -> cpu-cpuid.<cpuid flag>
    • pstate-turbo -> cpu-pstate.turbo
    • rdt-<rdt feature> -> cpu-rdt.<rdt feature>
• Support for config file (Configurability via a config file and command line flags #169). Currently with three configurable feature sources i.e. cpu (source/cpu: make cpuid configurable #224), kernel (Implement kernel version detection #157) and pci (Implement PCI feature source #168)
• Support for non-binary labels, with arbitrary values other than plain true
• PCI device detection (Implement PCI feature source #168)
• Kernel version detection (Implement kernel version detection #157)
• Kernel config option detection (Discover kconfig flags #146)
• Support for custom feature-detector hooks (Plugin mechanism for customer-specific labels #144)
• Support OS version detection (OS version detection #149, source/system: advertise major and minor OS version #211)
• Detection of hardware multithreading, such as Intel Hyper-Threading Technology (Implement cpu feature source #147)
• Arm64 support for CPUID detection (Add ARM64 support to cpuid #194)
• Validation of feature label names and values (Add validation for feature label values #199, Use k8s apimachinery for label validation #219)
• Detection of NVDIMM devices (source/memory: detect presence of NVDIMM devices #214)
• Get labels by reading from file in local source (Allow to get labels by reading files in local source #228)
• Detection of Intel SST-BF (Speed Select Technology - Base Frequency) (source/cpu: detect SST-BF #235)
• Make it possible to create feature labels in non-default namespace (Allow to change labels namespace #231). Currently possible for using the local source (hooks and files).

Miscellaneous

• Template specs converted from json to yaml
• Documentation updates fixes

Deployment

For complete documentation see the v0.4.0 release

For quick start, you can use the provided template specs to deploy the NFD release image with the default configuration in the default namespace:

export NFD_VERSION=v0.4.0
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/node-feature-discovery/$NFD_VERSION/nfd-master.yaml.template
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/node-feature-discovery/$NFD_VERSION/nfd-worker-daemonset.yaml.template

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[marquiz]

/remove-lifecycle stale

[jjacobelli]

Do you think we can wait for #231 too? I would like to have this in the next release

[marquiz]

Do you think we can wait for #231 too? I would like to have this in the next release

Yeah, sure. I think it's basically ready to go. I just want to test it on my own

[marquiz]

Updated changelog a bit. Also, added short deployment instructions

[marquiz]

#231 is now merged. I'm ready to go for a release

[jjacobelli]

Yes, looks good to me!

[marquiz]

I've doing verification, and haven't found any issues. #249 contains some documentation fixes. After that I would be ready to proceed

[zvonkok]

/lgtm wow, what a nice release :) a ton of features.

[zvonkok]

@marquiz Do you want to reference #175 and #177 in this release too, aren't those with this release "done"?

[marquiz]

#177 is not yet done, although I initially thought it would've been solved quite fast. I added a reference to both of these in the changelog above^

[marquiz]

#250 updates documentation and deployment examples

[marquiz]

Github release page:
https://github.com/kubernetes-sigs/node-feature-discovery/releases/tag/v0.4.0

[marquiz]

Release announcement:
https://groups.google.com/forum/#!topic/kubernetes-dev/8n4Cj5A-Nao