Release v0.6.0

[marquiz]

Release checklist:

• All OWNERS must LGTM the release proposal.
• Update the deployment templates (master, worker-daemonset, worker-job and combined)to use the new tagged container image
• An OWNER runs git tag -s $VERSION and insert the changelog into the tag description.
• An OWNER pushes the tag with git push $VERSION (this will also build and push a release container image to quay.io).
• Update the :latest virtual tag in quay.io to track the last stable (this) release.
• 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. Add a link to the release announcement here.
• Close this issue.

Changelog

Major changes

• New custom feature source (Support custom features #290). Introduces a new feature source that allows creating user-defined labels based on configurable matcher rules. See README for detailed description and examples.
• Support USB device discovery (Add support for USB device discovery #310). Adds a new configurable usb feature source advertising USB devices and a new UsbId rule type to the custom source. See the documentation of USB source and UsbId custom rule for more details.
• Experimental support for extended resources (master: add extended resource support #291). Makes it possible to configure nfd-master to advertise specific features as extended resources instead of node labels. See README for more details.
• PCI: add sriov.capable attribute for PCI devices that support SR-IOV (pci: add sriov.capable attribute #288)
• Change suggested nfd-master deployment from Daemonset to Deployment (Change nfd-master deployment mechanism from daemonset to deployment #294)
• Support run-time configuration file updates (Rework config handling #304)
• Perform network feature discovery under host sysfs (source/network: run discovery under /host-sys #317). Removes the need to use hostNetwork on nfd-worker pods.
• Support cpuid for ARM/Aarch32 (cpu: Add support for ARM/Aarch32 cpuid #322)

Miscellaneous

• Do not publish empty OS version labels (source/system: do not publish empty version labels #299)
• Handle forbidden symbols in kernel version label (Proposal kernel.go: Replace forbidden symbols and check format #309)
• Unify behaviour of --label-whitelist across nfd-worker and nfd-master (nfd-worker: fix --label-whitelist #307). On nfd-worker, the label namespace is now ignored, i.e. the filter is applied on the name part after /.
• Documentation improvements (README: note on avoiding a race condition with hooks #284, README: better document the usage of hooks and feature files #285, README: document node annotations #316, README: document E2E_TEST_CONFIG Makefile variable #323)
• Improved end-to-end tests and integration with the CI (e2e test integration in Travis CI #186, test/e2e: more comprehensive per-node testing #292)
• Update to klauspost/cpuid to v1.2.3 for improved CPUID detecttion (vendor: update klauspost/cpuid #279)
• Update to Kubernetes v.1.17 (go.mod: update kubernetes and its deps to v1.17.2 #282)

Deployment

For complete documentation see the v0.6.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.6.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

[marquiz]

@zvonkok @Ethyling what do you think about cutting a release? I udpated the changelog above.

I already created a PR updating the version tag in documentation and template specs (#310), but, it would be nice to get at least #316 merged before that. We could also consider #307 and #310 (ping @pmundt).

[pmundt]

#310 should now be ready to go (pong @marquiz).

[marquiz]

#310 should now be ready to go

Thanks! Merged. I updated changelog above accordingly.

[zvonkok]

@marquiz So the only one left is #307 as far as I can see all other merged from the above comment.

[marquiz]

Yes, that's right. I think we can skip #307 even if I consider that as a nice-to-have fix

[marquiz]

Changelog above updated.

Thanks @Ethyling for all the all the very responsive review work! We got in a lot of cleanups and CI improvements. I think we could merge #317 before closing this as it's virtually lgtm.

Before cutting a release, I also need to (re-)do some manual end-to-end verification because of all the latest changes.

[pmundt]

If it's possible to still sneak in #322 this would resolve the only outstanding issue I've run into for multi-arch builds.

[marquiz]

If it's possible to still sneak in #322

Yeah, sure. That is even such an nonintrusive patch. I really briefly looked at it. Might be good to get another peek (from me or somebody else).

[jjacobelli]

Do you want to merge #313 too?

[marquiz]

Do you want to merge #313 too?

We can do that but it's not high prio. I'll push a rebased version so you can take a look

[marquiz]

I did some release testing today and didn't find any issues. So far so good 🤞

What I'd like to check if we would be able to switch over to gcr.io (#177) already on this release.

[marquiz]

Looks like we still have to wait for that as the k8s.gcr.io vanity domain flip hasn't been completed, yet.

[marquiz]

...so I think we could cut a release with what we have at the moment. @Ethyling @zvonkok (?)

[jjacobelli]

Yeah I think we are good for this one 😄

[zvonkok]

/lgtm
Just verified that we have the PRs that we need for the upcoming work.

[marquiz]

Release page:
https://github.com/kubernetes-sigs/node-feature-discovery/releases/tag/v0.6.0

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