-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v0.16.4 #1800
Comments
marquiz
assigned kad, marquiz, zvonkok, PiotrProkop, jjacobelli, ArangoGutierrez, adrianchiris and fmuyassarov
Jul 18, 2024
I think we want to release #1799. We could also bump some deps |
And maybe #1801 |
/lgtm |
/close |
@marquiz: Closing this issue. In response to this:
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Release Checklist
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
prepare-release.sh
script above to the draft releasegit tag -s -m "NFD release $VERSION" $VERSION
git push $VERSION
gcr.io/k8s-staging-nfd/node-feature-discovery:$VERSION
https://kubernetes-sigs.github.io/node-feature-discovery/0.$MAJ/
registry.k8s.io/images/k8s-staging-nfd/images.yaml
to promote the container images (both "full" and "minimal" variants) to productionregistry.k8s.io/nfd/node-feature-discovery:$VERSION
) is available.which will also trigger a Helm repo index update to add the latest release
hack/prepare-release.sh $VERSION
but only committing README.md, and,submit a PR
Changelog
This patch release contains improvements to the Helm chart, adding configurable liveness and readiness probes for all daemons and configurable revision history limit for the nfd-worker and nfd-topology-updater.
Full Changelog: v0.16.3...v0.16.4
The text was updated successfully, but these errors were encountered: