Release v0.15.5

[marquiz]

trafficstars

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
• [ ] An OWNER runs git tag -s -m "NFD release $VERSION" $VERSION
• [ ] 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 registry.k8s.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 (registry.k8s.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.
• [ ] Close this issue

Changelog

This patch release fixes nfd-topology-updater on IPv6 clusters.

List of PRs

• go.mod: update dependencies (#1676)
• topology-updater: properly handle IPv6 from NODE_ADDRESS (#1732)

[adrianchiris]

lgtm

[PiotrProkop]

/lgtm

[jjacobelli]

/lgtm

[ArangoGutierrez]

/lgtm

[marquiz]

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

/close

[k8s-ci-robot]

@marquiz: Closing this issue.

In response to this:

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

/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-sigs/prow repository.