Labels

• 1.0

  Any issue that we want to land in 1.0. This is not normative.
• approved

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

  Consider this PR to be backported to the release branch
• backport/pr

  A backport PR which is target to a release branch.
• cla: no

  Indicates the PR's author has not signed the CLA.
• cla: yes

  Indicates the PR's author has signed the CLA.
• comp/source
• comp/trigger
• dependencies

  Pull requests that update a dependency file
• 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.
• Epic

  Epics to group issues
• good first issue

  Denotes an issue ready for a new contributor.
• help wanted

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

  This doesn't seem right
• 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/cncf-after
• kind/cncf-blocked
• kind/cncf-infra
• kind/compatibility

  Issues type regarding compatibility of client
• kind/deprecation

  Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
• kind/doc

  Issues and pull requests for documentations
• kind/documentation
• kind/duplicate

  This issue or pull request already exists
• kind/enhancement