Release v0.4.0

[ArangoGutierrez]

Release Checklist

• [ ] All OWNERS must LGTM the release proposal
• [x] Verify that the changelog in this issue is up-to-date
• [x] For major releases (v0.$MAJ.0), an OWNER creates a release branch with git branch release-0.$MAJ master
• [x] An OWNER creates a vanilla release branch from master and pushes it with git push release-0.$MAJ
• [x] An OWNER creates an annotated and signed tag with git tag -a -s $VERSION and inserts the changelog into the tag description.
• [x] An OWNER pushes the tag with git push $VERSION This will trigger prow to build and publish a staging container image gcr.io/k8s-staging-nfd/node-feature-discovery-operator:$VERSION
• [x] Submit a PR against k8s.io, updating k8s.gcr.io/images/k8s-staging-nfd/images.yaml to promote the container image to production
• [x] Wait for the PR to be merged and verify that the image (k8s.gcr.io/nfd/node-feature-discovery-operator:$VERSION) is available.
• [x] Write the change log into the Github release info.
• [x] Add a link to the tagged release in this issue.
• [x] Create a new bundle at https://github.com/k8s-operatorhub/community-operators
• [x] Send an announcement email to kubernetes-dev@googlegroups.com with the subject [ANNOUNCE] node-feature-discovery-operator $VERSION is released
• [x] Add a link to the release announcement in this issue
• [x] Close this issue

Changelog

• Drop operand.namespace from NodeFeatureDiscoveries CRD #115
• Enable TopologyUpdater worker deployment #116
• Enable Status report to the CR instance #117
• Enable Finalizers for the CR instance #117
• Add new CRD's NodeResourceTopology and NodeFeatureRules #119
• Update dependencies to latest stable as of release cut date #120

[ArangoGutierrez]

1. https://github.com/kubernetes-sigs/node-feature-discovery-operator/pull/115
2. https://github.com/kubernetes-sigs/node-feature-discovery-operator/pull/116
3. https://github.com/kubernetes-sigs/node-feature-discovery-operator/pull/117
4. https://github.com/kubernetes-sigs/node-feature-discovery-operator/pull/119
5. https://github.com/kubernetes-sigs/node-feature-discovery-operator/pull/120
6. https://github.com/kubernetes-sigs/node-feature-discovery-operator/pull/127

[ArangoGutierrez]

https://github.com/kubernetes/k8s.io/pull/3418

[ArangoGutierrez]

[eduardo@fedora k8s.io]$ skopeo list-tags docker://k8s.gcr.io/nfd/node-feature-discovery-operator  |grep v0.4
        "v0.4.0",
        "v0.4.0-minimal"

[ArangoGutierrez]

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

[ArangoGutierrez]

https://github.com/k8s-operatorhub/community-operators/pull/785

[ArangoGutierrez]

https://github.com/kubernetes-sigs/node-feature-discovery-operator/issues/66

[ArangoGutierrez]

https://groups.google.com/a/kubernetes.io/g/dev/c/I_8Tg-s1_EM

[ArangoGutierrez]

/close

[k8s-ci-robot]

@ArangoGutierrez: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/node-feature-discovery-operator/issues/118#issuecomment-1043319282): >/close 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/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.