Release v0.4.2

[marquiz]

Release Checklist

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

Changelog

[ArangoGutierrez]

#145

[ArangoGutierrez]

Changelog:

• Update kubebuilder rbac #144
• Run nfd-master as Deployment #141

[ArangoGutierrez]

kubernetes/k8s.io#3677

[ArangoGutierrez]

{
    "Repository": "k8s.gcr.io/nfd/node-feature-discovery-operator",
    "Tags": [
        "v0.2.0",
        "v0.3.0",
        "v0.3.0-minimal",
        "v0.4.0",
        "v0.4.0-minimal",
        "v0.4.1",
        "v0.4.1-minimal",
        "v0.4.2",
        "v0.4.2-minimal"
    ]
}

[ArangoGutierrez]

#147

[ArangoGutierrez]

Tag 0.4.2 and 0.4.3 #149
Will be released at release-0.4.3

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