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

awaiting review

cherrypick-approved

Indicates a cherrypick PR into a release branch has been approved by the release branch manager.

cherrypick-candidate

Denotes a PR to master as a candidate for cherry picking into a release branch.

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

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

committee/conduct

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

committee/steering

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

Contribution Allowed

If the contributor has signed the DCO or the CNCF CLA (prior to the move to a DCO).

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.

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

good first issue

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

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

Categorizes issue or PR as related to a bug.

Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Categorizes issue or PR as related to design.

kind/documentation

Categorizes issue or PR as related to documentation.

Categorizes issue or PR as related to a new feature.

Categorizes issue or PR as related to a flaky test.

Indicates that a PR is ready to be merged.

lifecycle/frozen

Indicates that an issue or PR should not be auto-closed due to staleness.

lifecycle/rotten

Denotes an issue or PR that has aged beyond stale and will be auto-closed.

lifecycle/stale

Denotes an issue or PR has remained open with no activity and has become stale.

needs-ok-to-test

Indicates a PR that requires an org member to verify it is safe to test.

Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Indicates an issue lacks a `sig/foo` label and requires one.

priority/awaiting-more-evidence

Lowest priority. Possibly useful, but not yet enough support to actually get it done.

priority/backlog

Higher priority than priority/awaiting-more-evidence.

priority/critical-urgent

Highest priority. Must be actively worked on as someone's top priority right now.

priority/failing-test

Automatically filed frequently failing test. Needs to be investigated.

priority/important-longterm

Important over the long term, but may not be staffed and/or may need multiple releases to complete.

priority/important-soon

Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

queue/blocks-others

queue/critical-fix

queue/multiple-rebases

Denotes a PR that will be considered when it comes time to generate release notes.

release-note-action-required

Denotes a PR that introduces potentially breaking changes that require user action.

release-note-none

Denotes a PR that doesn't merit a release note.

retest-not-required

Indicates that a PR doesn't need to be retested prior to merge.

retest-not-required-docs-only

Indicates that a PR doesn't need to be retested prior to merge because it only changes docs.

sig/api-machinery

Categorizes an issue or PR as relevant to sig-api-machinery.

Categorizes an issue or PR as relevant to sig-apps.

sig/architecture

Categorizes an issue or PR as relevant to sig-architecture.

Categorizes an issue or PR as relevant to sig-auth.

sig/autoscaling

Categorizes an issue or PR as relevant to sig-autoscaling.

Categorizes an issue or PR as relevant to sig-aws.

Categorizes an issue or PR as relevant to sig-azure.

Categorizes an issue or PR as relevant to sig-big-data.

Categorizes an issue or PR as relevant to sig-cli.

sig/cloud-provider

Categorizes an issue or PR as relevant to sig-cloud-provider.

sig/cluster-lifecycle

Categorizes an issue or PR as relevant to sig-cluster-lifecycle.

sig/cluster-ops

Categorizes an issue or PR as relevant to sig-cluster-ops.

sig/contributor-experience

Categorizes an issue or PR as relevant to sig-contributor-experience.

Categorizes an issue or PR as relevant to sig-docs.

Categorizes an issue or PR as relevant to sig-gcp.

Categorizes an issue or PR as relevant to sig-ibmcloud.

sig/instrumentation

Categorizes an issue or PR as relevant to sig-multicluster.

sig/multicluster

Categorizes an issue or PR as relevant to sig-multicluster.

Categorizes an issue or PR as relevant to sig-network.

Categorizes an issue or PR as relevant to sig-node.

Categorizes an issue or PR as relevant to sig-onprem.

Categorizes an issue or PR as relevant to sig-openstack.

Categorizes an issue or PR as relevant to sig-pm.

Categorizes an issue or PR as relevant to sig-release.

sig/scalability

Categorizes an issue or PR as relevant to sig-scalability.

Categorizes an issue or PR as relevant to sig-scheduling.

sig/service-catalog

Categorizes an issue or PR as relevant to sig-service-catalog.

Categorizes an issue or PR as relevant to sig-storage.

Categorizes an issue or PR as relevant to sig-testing.

Categorizes an issue or PR as relevant to sig-ui.

Categorizes an issue or PR as relevant to sig-vmware.

Categorizes an issue or PR as relevant to sig-windows.

Denotes a PR that changes 100-499 lines, ignoring generated files.

Denotes a PR that changes 30-99 lines, ignoring generated files.

Denotes a PR that changes 10-29 lines, ignoring generated files.

Denotes a PR that changes 500-999 lines, ignoring generated files.

Denotes a PR that changes 0-9 lines, ignoring generated files.

Denotes a PR that changes 1000+ lines, ignoring generated files.

status/approved-for-milestone

Used during release burndown. Denotes an issue or PR is approved to be part of the release

status/in-progress

Used during release burndown. Denotes that an issue is actively being worked.

status/in-review

Used during release burndown. Denotes that a fix for an issue is actively being reviewed.

triage/duplicate

Indicates an issue is a duplicate of other open issue.

triage/needs-information

Indicates an issue needs more information in order to work on it.

triage/not-reproducible

Indicates an issue can not be reproduced as described.

Indicates an issue that is a support question.

triage/unresolved

Indicates an issue that can not or will not be resolved.

Categorizes an issue or PR as relevant to wg-app-def.

Categorizes an issue or PR as relevant to wg-apply.

Categorizes an issue or PR as relevant to wg-cluster-api.

wg/container-identity

Categorizes an issue or PR as relevant to wg-container-identity.

Categorizes an issue or PR as relevant to wg-iot-edge.

wg/kubeadm-adoption

Categorizes an issue or PR as relevant to wg-kubeadm-adoption.

wg/machine-learning

Categorizes an issue or PR as relevant to wg-machine-learning.

wg/multitenancy

Categorizes an issue or PR as relevant to wg-multitenancy.

Categorizes an issue or PR as relevant to wg-policy.

wg/resource-management

Categorizes an issue or PR as relevant to wg-resource-management.

No labels found. Sorry about that.