Release v0.11.2

[marquiz]

Release Checklist

• All OWNERS must LGTM the release proposal
• Verify that the changelog in this issue is up-to-date
• For major releases (v0.$MAJ.0) create new release branch
  • an OWNER creates a vanilla release branch with
    git branch release-0.$MAJ master
  • An OWNER pushes the new release branch with
    git push release-0.$MAJ
• 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 against the release branch
• An OWNER prepares a draft release
  • Create a draft release at Github releases page
  • Write the change log into the draft release
  • Upload release artefacts generated by prepare-release.sh script above to the draft release
• An OWNER runs
  git tag -s $VERSION
  and inserts the changelog into the tag description.
• 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-discovery/0.$MAJ/
• 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
• Wait for the PR to be merged and verify that the image (k8s.gcr.io/nfd/node-feature-discovery:$VERSION) is available.
• Publish the draft release prepared at the Github releases page
  which will also trigger a Helm repo index update to add the latest release
• Add a link to the tagged release in this issue.
• Send an announcement email to dev@kubernetes.io with the subject [ANNOUNCE] node-feature-discovery $VERSION is released
• Add a link to the release announcement in this issue
• For a major release (or a point release of the latest major release), update README in master branch
  • Update references e.g. by running scripts/prepare-release.sh $VERSION but only committing README.md, and,
    submit a PR
  • Wait for the PR to be merged
• 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.
• Close this issue

Changelog

This point release fixes an issue with NodeFeatureRule templating. It also provides a fresh build with updated golang and updated base image addressing an issue with cve security scan (#853).

List of PRs

• docs: update x86 cpuid feature list ([release-0.11] docs: update x86 cpuid feature list #823)
• docs: fix operator deployment instructions ([release-0.11] docs: fix operator deployment instructions #813)
• docs: small typo fix in cpuid feature list ([release-0.11] docs: small typo fix in cpuid feature list #826)
• dockerfile: bump builder image to golang v1.17.13 ([release-0.11] dockerfile: bump builder image to golang v1.17.13 #869)
• Fix templates for NodeFeatureRule with MatchAny ([release-0.11] Fix templates for NodeFeatureRule with MatchAny #872)

[marquiz]

• build with latest golang ([release-0.11] dockerfile: bump builder image to golang v1.17.13 #869)
• fix templating (backport Fix templates for NodeFeatureRule with MatchAny #865)
• fresh build to address CVE scan lists high vulnerability against latest image k8s.gcr.io/nfd/node-feature-discovery:v0.11.1 #853

[ArangoGutierrez]

👍🏽

[marquiz]

ping @Ethyling @adrianchiris
@zvonkok is on vacation

[jjacobelli]

👍

[adrianchiris]

+1

[ArangoGutierrez]

kubernetes/k8s.io#4130 (review)

[marquiz]

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

Release announcement:
https://groups.google.com/a/kubernetes.io/g/dev/c/1ahm6w--VLE

[ArangoGutierrez]

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

Release announcement: https://groups.google.com/a/kubernetes.io/g/dev/c/1ahm6w--VLE

/close ?

[marquiz]

Yeah, now all boxes ticked
/close

[k8s-ci-robot]

@marquiz: Closing this issue.

In response to this:

Yeah, now all boxes ticked
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.