Labels

• api-review

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

  Indicates a PR has been approved by an approver from all required OWNERS files.
• area/dependency

  Issues or PRs related to dependency changes
• area/licensing

  Issues or PRs related to Kubernetes licensing
• backport-risk-assessed
• bugzilla/invalid-bug

  Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting.
• bugzilla/severity-high
• bugzilla/severity-medium
• bugzilla/severity-urgent
• bugzilla/valid-bug

  Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting.
• cherry-pick-approved

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

  DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.
• 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

  Indicates that a PR is not yet approved to merge into a release branch.
• do-not-merge/hold

  Indicates that a PR should not merge because someone has issued a /hold command.
• 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

  Indicates that a PR should not merge because it's missing one of the release note labels.
• do-not-merge/work-in-progress

  Indicates that a PR should not merge because it is a work in progress.
• good first issue

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

  Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
• kind/api-change

  Categorizes issue or PR as related to adding, removing, or otherwise changing an API
• kind/bug

  Categorizes issue or PR as related to a bug.
• kind/cleanup

  Categorizes issue or PR as related to cleaning up code, process, or technical debt.
• kind/dependency-change

  Categorizes issue or PR as related to changing dependencies
• kind/design

  Categorizes issue or PR as related to design.
• kind/documentation

  Categorizes issue or PR as related to documentation.
• kind/failing-test

  Categorizes issue or PR as related to a consistently or frequently failing test.
• kind/feature

  Categorizes issue or PR as related to a new feature.
• kind/flake

  Categorizes issue or PR as related to a flaky test.
• lgtm

  Indicates that a PR is ready to be merged.