Labels

• api-review

  api-review

  Categorizes an issue or PR as actively needing an API review.

• approved

  approved

  Indicates a PR has been approved by an approver from all required OWNERS files.

• area/community-meeting

  area/community-meeting

  Issues or PRs that should potentially be discussed in a Kubernetes community meeting.

• area/dependency

  area/dependency

  Issues or PRs related to dependency changes

• area/kro

  area/kro

  Issues or PRs related to KRO

• area/provider/aws

  area/provider/aws

  Issues or PRs related to aws provider

• area/provider/azure

  area/provider/azure

  Issues or PRs related to azure provider

• area/provider/digitalocean

  area/provider/digitalocean

  Issues or PRs related to digitalocean provider

• area/provider/gcp

  area/provider/gcp

  Issues or PRs related to gcp provider

• area/provider/ibmcloud

  area/provider/ibmcloud

  Issues or PRs related to ibmcloud provider

• area/provider/openstack

  area/provider/openstack

  Issues or PRs related to openstack provider

• area/provider/vmware

  area/provider/vmware

  Issues or PRs related to vmware provider

• cherry-pick-approved

  cherry-pick-approved

  Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.

• cncf-cla: no

  cncf-cla: no

  Indicates the PR's author has not signed the CNCF CLA.

• cncf-cla: yes

  cncf-cla: yes

  Indicates the PR's author has signed the CNCF CLA.

• committee/code-of-conduct

  committee/code-of-conduct

  Denotes an issue or PR intended to be handled by the code of conduct committee.

• committee/security-response

  committee/security-response

  Denotes an issue or PR intended to be handled by the product security committee.

• committee/steering

  committee/steering

  Denotes an issue or PR intended to be handled by the steering committee.

• dependencies

  dependencies

  Pull requests that update a dependency file

• do-not-merge

  do-not-merge

  DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.

• do-not-merge/blocked-paths

  do-not-merge/blocked-paths

  Indicates that a PR should not merge because it touches files in blocked paths.

• do-not-merge/cherry-pick-not-approved

  do-not-merge/cherry-pick-not-approved

  Indicates that a PR is not yet approved to merge into a release branch.

• do-not-merge/hold

  do-not-merge/hold

  Indicates that a PR should not merge because someone has issued a /hold command.

• do-not-merge/invalid-commit-message

  do-not-merge/invalid-commit-message

  Indicates that a PR should not merge because it has an invalid commit message.

• do-not-merge/invalid-owners-file

  do-not-merge/invalid-owners-file

  Indicates that a PR should not merge because it has an invalid OWNERS file in it.

• do-not-merge/release-note-label-needed

  do-not-merge/release-note-label-needed

  Indicates that a PR should not merge because it's missing one of the release note labels.

• do-not-merge/work-in-progress

  do-not-merge/work-in-progress

  Indicates that a PR should not merge because it is a work in progress.

• good first issue

  good first issue

  Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

• help wanted

  help wanted

  Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

• kind/api-change

  kind/api-change

  Categorizes issue or PR as related to adding, removing, or otherwise changing an API