Release v0.13.1

[marquiz]

Release Checklist

• All OWNERS must LGTM the release proposal
• Verify that the changelog in this issue is up-to-date
• 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
  • 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 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.
• Send an announcement email to [email protected] 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 hack/prepare-release.sh $VERSION but only committing README.md, and,
    submit a PR
  • Wait for the PR to be merged
• Close this issue

Changelog

[zvonkok]

/lgtm

[ArangoGutierrez]

/lgtm

[fmuyassarov]

+1

[adrianchiris]

/lgtm

[PiotrProkop]

+1

[ArangoGutierrez]

• [release-0.13] nfd-master: reject malformed extended resource dynamic capacity assignment #1179
• [release-0.13] pkg/nfd-master/nfd-master.go: Fix typo #1177
• [release-0.13] nfd-master: fix a crash when processing NodeFeatureRules #1174
• [release-0.13] nfd-master: fix -prune #1165

[marquiz]

Plus

• [release-0.13] nfd-master: support noPublish with -prune #1163

I'm not aware of anything else in the pipeline

[PiotrProkop]

Plus:

• nfd-topology-updater: fix wrong kubelet_internal_checkpoint path and compare basename to full path #1167

[ArangoGutierrez]

Plus:

• nfd-topology-updater: fix wrong kubelet_internal_checkpoint path and compare basename to full path #1167

Does the PR that introduced this situation was part of V0.13? if older than that, maybe this can be just a nice fix for V0.14

[PiotrProkop]

Plus:

• nfd-topology-updater: fix wrong kubelet_internal_checkpoint path and compare basename to full path #1167

Does the PR that introduced this situation was part of V0.13? if older than that, maybe this can be just a nice fix for V0.14

Reactive updates was part of v0.13:

• topology-updater: reactive updates #1031

[ArangoGutierrez]

ok then this qualifies for v0.13.1 IMO

[jjacobelli]

/lgtm

[ArangoGutierrez]

Final changelog for v0.13.1

CHANGELOG

• [release-0.13] nfd-master: reject malformed extended resource dynamic capacity assignment #1179
• [release-0.13] pkg/nfd-master/nfd-master.go: Fix typo #1177
• [release-0.13] nfd-master: fix a crash when processing NodeFeatureRules #1174
• [release-0.13] nfd-master: fix -prune #1165
• [release-0.13] nfd-master: support noPublish with -prune #1163
• [release-0.13] nfd-topology-updater: fix wrong kubelet_internal_checkpoint path and compare basename to full path #1183

If there are no further objections I'll start the release process tomorrow.

[ArangoGutierrez]

#1195

[ArangoGutierrez]

Release cut is paused for today, image promotion is broken

[ArangoGutierrez]

kubernetes/k8s.io#5183

[ArangoGutierrez]

eduardo@fedora:~$ polluntiltrue "skopeo list-tags docker://registry.k8s.io/nfd/node-feature-discovery |grep  v0.13.1" 3 
        "v0.13.1",
        "v0.13.1-full",
        "v0.13.1-minimal",

[ArangoGutierrez]

https://github.com/kubernetes-sigs/node-feature-discovery/releases/tag/v0.13.1

[ArangoGutierrez]

#1197

[ArangoGutierrez]

https://groups.google.com/a/kubernetes.io/g/dev/c/x-OcenWW7ZI/m/sG5MEfaBAQAJ

[ArangoGutierrez]

/close

[k8s-ci-robot]

@ArangoGutierrez: Closing this issue.

In response to this:

/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.