Release v0.11.0

[marquiz]

Release Checklist

• [ ] All OWNERS must LGTM the release proposal
• [x] Verify that the changelog in this issue is up-to-date
• [x] For major releases (v0.$MAJ.0) create new release branch
  • [x] an OWNER creates a vanilla release branch with git branch release-0.$MAJ master
  • [x] An OWNER pushes the new release branch with git push release-0.$MAJ
• [x] Run scripts/prepare-release.sh $VERSION to turn references to point to the upcoming release (README, deployment templates, docs configuration, test/e2e flags), submit a PR agains the release branch
• An OWNER prepares a draft release
  • [x] Create a draft release at Github releases page
  • [x] Write the change log into the draft release
  • [x] Upload release artefacts generated by prepare-release.sh script above to the draft release
• [x] An OWNER runs git tag -s $VERSION and inserts the changelog into the tag description.
• [x] An OWNER pushes the tag with git push $VERSION
  • Triggers prow to build and publish a staging container image gcr.io/k8s-staging-nfd/node-feature-discovery:$VERSION
  • Triggers build of the documentation and publish it at https://kubernetes-sigs.github.io/node-feature
• [x] Submit a PR against k8s.io, updating k8s.gcr.io/images/k8s-staging-nfd/images.yaml to promote the container images (both "full" and "minimal" variants) to production
• [x] Wait for the PR to be merged and verify that the image (k8s.gcr.io/nfd/node-feature-discovery:$VERSION) is available.
• [x] Publish the draft release prepared at the Github releases page which will also trigger a Helm repo index update to add the latest release
• [x] Add a link to the tagged release in this issue.
• [x] Send an announcement email to dev@kubernetes.io with the subject [ANNOUNCE] node-feature-discovery $VERSION is released
• [x] Add a link to the release announcement in this issue
• [x] For a major release (or a point release of the latest major release), update README in master branch
  • [x] Update references e.g. by running scripts/prepare-release.sh $VERSION but only committing README.md, and, submit a PR
  • [x] Wait for the PR to be merged
• [x] For a major release, create an unannotated devel tag in the master branch, on the first commit that gets merged after the release branch has been created (presumably the README update commit above), and, push the tag: DEVEL=v0.$(($MAJ+1)).0-devel; git tag $DEVEL master && git push $DEVEL This ensures that the devel builds on the master branch will have a meaningful version number.
• [x] Close this issue

Changelog

• Detection of CPU model
• Detect Intel Control-flow Enforcement Technology (CET)
• Detect intel-iommu/version attribute of PCI devices
• Detect IBM Secure Execution (S390x)
• Helm chart:
  • Support configuring -resource-labels for nfd-master
  • Configurable annotations to DaemonSet (nfd-master) and Deployment (nfd-worker)
  • Create ServiceAccount for nfd-worker

List of PRs

• README: bump to v0.10.0 (#720)
• scripts/update-gh-pages: fix symlink to stable version (#724)
• go.mod: bump kubernetes to v1.23.1 (#725)
• github: re-organize the release process slightly (#721)
• Fix GoLinter Issues in the files (#711)
• Multi ARCH build amd64, arm64 (#698)
• Adding missing target dep (#728)
• cloudbuild.yaml: set HOME to /root (#730)
• cloudbuild.yaml: double the timeout (#731)
• cloudbuild.yaml: increase timeout to 2400s (#733)
• cloudbuild.yaml: increase timeout to 1 hour (#734)
• cloudbuild.yaml: increase timeout to 1h 20min (#735)
• Increase timeout in test setups (#738)
• scripts: configure docker auth in push-image.sh (#739)
• cloudbuild.yaml: upgrade machine type to n1-highcpu-8 (#740)
• scripts/test-infra: separate task for multiarch image build (#742)
• nfd-master: print gRPC server error correctly (#732)
• nfd-master: do graceful stop of gRPC server (#736)
• cloudbuild.yaml: decrease timeout to 25 minutes (#741)
• docs: clarify deployment requirements (#745)
• docs: drop topology-updater cmdline help from developer guide (#748)
• README: point to v0.10.1 (#753)
• docs: update helm document to match values.yaml (#727)
• docs: fix operator deployment instructions (#726)
• scripts/prepare-release: fix upating of readme (#755)
• docs: re-fix operator deployment instructions (#762)
• docs: use new custom rule format in worker config reference (#754)
• go.mod: update to klauspost/cpuid/v2@v2.0.11 (#771)
• docs: Update default K8S_NAMESPACE (#773)
• tls: require min TLS version 1.3 (#781)
• Add ServiceAccount for nfd-worker (#782)
• Additional Lint Fixes in Codebase (#779)
• Fixed the incorrect references (#769)
• source/pci: detect intel-iommu/version (#716)
• topologyupdater: Prevent crash with incorrect node id (#783)
• deployment/helm: add resourceLabels to master args (#793)
• Fix a couple typos (#796)
• apis/nfd: empty match expression set returns no features for templates (#787)
• helm: add annotations to daemonset and deployment (#794)
• Add cpu-model feature detection (#792)
• cpu: Discover IBM Secure Execution (#790)

[marquiz]

Trying to start a more predictable and constant release cadence. Release whatever new features we have (even if the list is short) so that users can take them into use

[ArangoGutierrez]

Any milestones for this PR? (pending PR's)

[ArangoGutierrez]

/lgtm

[marquiz]

Any milestones for this PR? (pending PR's)

https://github.com/kubernetes-sigs/node-feature-discovery/milestone/5

Just small fixes. Moved the bigger stuff to v0.12.0

[jjacobelli]

/lgtm Nice release once again!

[adrianchiris]

/lgtm !

[marquiz]

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

Release announcement: https://groups.google.com/a/kubernetes.io/g/dev/c/m4LkVD8qMQY/m/orkEw4hhBwAJ

[marquiz]

/close

[k8s-ci-robot]

@marquiz: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/node-feature-discovery/issues/786#issuecomment-1081741057): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.