Release v0.16.5

[marquiz]

Release Checklist

• [x] Verify that the changelog in this issue is up-to-date
• [x] Run hack/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
  • 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 -m "NFD release $VERSION" $VERSION
• [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-discovery/0.$MAJ/
• [x] Submit a PR against k8s.io, updating registry.k8s.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 (registry.k8s.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] For a point release of the latest newest release branch, update README in master branch
  • [x] Update references e.g. by running hack/prepare-release.sh $VERSION but only committing README.md, and, submit a PR
  • [x] Wait for the PR to be merged
• [x] Close this issue

Changelog

Fixes an nfd-master memory leak on re-configure events when leader election is enabled.

[marquiz]

At least fix #1841 (#1848)

[ArangoGutierrez]

Maybe also https://github.com/kubernetes-sigs/node-feature-discovery/pull/1878?

[marquiz]

Maybe also #1878?

We could take that. But host networks also requires #1885 which is a bit more controversial for a patch release

[tobiasgiese]

But host networks also requires #1885 which is a bit more controversial for a patch release

From my perspective, this PR doesn’t introduce any changes to the core logic or default behavior, so the impact should be minimal. The Helm value retains a default setting if not explicitly configured. Given that, I believe it should be safe to include in the patch release.

[marquiz]

@tobiasgiese fair enough. I agree that #1885 is very low risk, let's cherry-pick

[marquiz]

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

[tobiasgiese]

Also the helm repo is published

❯ helm search repo nfd
NAME                        CHART VERSION   APP VERSION DESCRIPTION
nfd/node-feature-discovery  0.16.5          v0.16.5     Detects hardware features available on each nod...

Thanks alot for your effort and the quick release!

[tobiasgiese]

/close in favor of https://github.com/kubernetes-sigs/node-feature-discovery/pull/1909

[k8s-ci-robot]

@tobiasgiese: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/node-feature-discovery/issues/1849#issuecomment-2413386745): >/close >in favor of https://github.com/kubernetes-sigs/node-feature-discovery/pull/1909 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.