Closed marquiz closed 1 year ago
See milestone v0.14. Annotations will likely not happen so there's only metrics support to be finished. We could cut the release in mid-July
@marquiz can we add this issue https://github.com/kubernetes-sigs/node-feature-discovery/issues/1254 to the v0.14
milestone? I'll work on it this week.
/assign @PiotrProkop @fmuyassarov
Milestone v0.14 will be ready today starting Release cut process
Milestone V0.14 is complete, proceeding to cut
[eduardo@fedora node-feature-discovery]$ skopeo list-tags docker://registry.k8s.io/nfd/node-feature-discovery |grep 0.14
"v0.14.0-full",
"v0.14.0-minimal",
Release Checklist
git branch release-0.$MAJ master
git push release-0.$MAJ
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 branchprepare-release.sh
script above to the draft releasegit tag -s $VERSION
and inserts the changelog into the tag description.git push $VERSION
gcr.io/k8s-staging-nfd/node-feature-discovery:$VERSION
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.dev@kubernetes.io
with the subject[ANNOUNCE] node-feature-discovery $VERSION is released
hack/prepare-release.sh $VERSION
but only committing README.md, and, submit a PRDEVEL=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.What's new
NodeFeature API
The NodeFeature API is now enabled by default. The new CRD-based API replaces the previous gRPC-based communication between nfd-master and nfd-worker and, reducing network traffic and allows changes in NodeFeatureRules to take effect immediately (independent of the sleep-interval of nfd-worker). NodeFeature API can also be used to implement 3rd party extensions, see customization guide for more details.
Garbage collection of stale NodeFeature objects was added in the form of nfd-gc daemon.
The gRPC API is now deprecated and will be removed in a future release. The related command-line flags are also deprecated (and don't have any effect when NodeFeature API is in use):
-ca-file
,-cert-file
,-key-file
,-port
,-verify-node-name
-ca-file
,-cert-file
,-key-file
,-server
,-server-name-override
Metrics
NFD now provides Prometheus metrics for better observability. Also, the Helm and kustomize deployments support enabling metrics collection with the Prometheus operator. See the documentation for more information about the available metrics and deployment instructions.
Hooks disabled by default
The deprecation of nfd-worker hooks continues, disabling them by default in v0.14. Potential users of hooks are encouraged to switch to use the NFD CRDs (NodeFeature and NodeFeatureRule) or feature files. Hooks can still be enabled with the
sources.local.hooksEnabled
configuration option.Feature files
Expiry time: NFD now supports specifying an expiry time for the features specified in a feature file, providing better lifecycle management for the feature labels. See the documentation for more details.
Size limit: There is now a 64kB size limit for feature files.
Miscellaneous
NodeFeatureRule API
Dynamic values for labels is now supported by using the
@
notation, see documentation for more details.NFD-Master
-nfd-api-parallelism
flagCPU features
Detection of Intel TDX guests is now supported.
Logging
The project was migrated structured logging, making log messages more consistent, better machine parseable and enables future improvements in logging.
Support policy
The project now officially documented it's supported versions and deprecation policy, see the documentation for details.
List of PRs