This file was auto-generated based on the contents of a labels.yaml that applies org-wide to the kubernetes github org
| Name | Description | Added By | Notes |
|---|---|---|---|
committee/conduct |
This is an issue or pull request intended for the (as of yet non-existent) code of conduct committee to deal with | prow label plugin | |
committee/steering |
This is an issue or pull request intended for the steering committee to deal with | prow label plugin | |
kind/bug |
issue or PR is related to a bug, applied by the /kind command by the prow label plugin | prow label plugin | |
kind/documentation |
issue or PR is related to documentation, applied by the /kind command by the prow label plugin | prow label plugin | |
kind/feature |
issue or PR is related to a new feature, applied by the /kind command by the prow label plugin | prow label plugin | |
lifecycle/frozen |
issue or PR should not be auto-closed, applied by the /lifecycle command by the prow plugin "lifecycle" | prow lifecycle plugin | was previously "keep-open", |
lifecycle/rotten |
issue or PR has aged beyond lifecycle/rotten and will be closed, applied by fejta-bot | prow lifecycle plugin | |
lifecycle/stale |
issue or PR has remained open with no activity for too long and has become stale, applied by the /lifecycle command by the lifecycle prow plugin | prow lifecycle plugin | was previously "stale", |
priority/awaiting-more-evidence |
Lowest priority. Possibly useful, but not yet enough support to actually get it done. These are mostly place-holders for potentially good ideas, so that they don't get completely forgotten, and can be referenced /deduped every time they come up. | prow label plugin | |
priority/backlog |
Higher priority than priority/awaiting-more-evidence. There appears to be general agreement that this would be good to have, but we may not have anyone available to work on it right now or in the immediate future. Community contributions would be most welcome in the mean time (although it might take a while to get them reviewed if reviewers are fully occupied with higher priority issues, for example immediately before a release). | prow label plugin | |
priority/critical-urgent |
Highest priority. Must be actively worked on as someone's top priority right now. Stuff is burning. If it's not being actively worked on, someone is expected to drop what they're doing immediately to work on it. Team leaders are responsible for making sure that all the issues, labeled with this priority, in their area are being actively worked on. Examples include user-visible bugs in core features, broken builds or tests and critical security issues. | prow label plugin | |
priority/failing-test |
TBD this should be replaced with kind/failing-test. Automatically filed frequently failing test. Needs to be investigated. | prow label plugin | |
priority/important-longterm |
Important over the long term, but may not be currently staffed and/or may require multiple releases to complete. | prow label plugin | |
priority/important-soon |
Lower priority than priority/critical-urgent. Must be staffed and worked on either currently, or very soon, ideally in time for the next release. | prow label plugin | |
sig/api-machinery |
issues or pr's relevant to sig-api-machinery | prow label plugin | |
sig/apps |
issues or pr's relevant to sig-apps | prow label plugin | |
sig/architecture |
issues or pr's relevant to sig-architecture | prow label plugin | |
sig/auth |
issues or pr's relevant to sig-auth | prow label plugin | |
sig/autoscaling |
issues or pr's relevant to sig-autoscaling | prow label plugin | |
sig/aws |
issues or pr's relevant to sig-aws | prow label plugin | |
sig/azure |
issues or pr's relevant to sig-azure | prow label plugin | |
sig/big-data |
issues or pr's relevant to sig-big-data | prow label plugin | |
sig/cli |
issues or pr's relevant to sig-cli | prow label plugin | |
sig/cluster-lifecycle |
issues or pr's relevant to sig-cluster-lifecycle | prow label plugin | |
sig/cluster-ops |
issues or pr's relevant to sig-cluster-ops | prow label plugin | |
sig/contributor-experience |
issues or pr's relevant to sig-contributor-experience | prow label plugin | |
sig/docs |
issues or pr's relevant to sig-docs | prow label plugin | |
sig/gcp |
issues or pr's relevant to sig-gcp | prow label plugin | |
sig/instrumentation |
issues or pr's relevant to sig-instrumentation | prow label plugin | |
sig/multicluster |
issues or pr's relevant to sig-multicluster | prow label plugin | was previously "sig/federation", "sig/federation (deprecated - do not use)", |
sig/network |
issues or pr's relevant to sig-network | prow label plugin | |
sig/node |
issues or pr's relevant to sig-node | prow label plugin | |
sig/onprem |
issues or pr's relevant to sig-onprem | prow label plugin | |
sig/openstack |
issues or pr's relevant to sig-openstack | prow label plugin | |
sig/release |
issues or pr's relevant to sig-release | prow label plugin | |
sig/rktnetes |
issues or pr's relevant to sig-rktnetes | prow label plugin | |
sig/scalability |
issues or pr's relevant to sig-scalability | prow label plugin | |
sig/scheduling |
issues or pr's relevant to sig-scheduling | prow label plugin | |
sig/service-catalog |
issues or pr's relevant to sig-service-catalog | prow label plugin | |
sig/storage |
issues or pr's relevant to sig-storage | prow label plugin | |
sig/testing |
issues or pr's relevant to sig-testing | prow label plugin | |
sig/ui |
issues or pr's relevant to sig-ui | prow label plugin | |
sig/vmware |
issues or pr's relevant to sig-vmware | prow label plugin | |
sig/windows |
issues or pr's relevant to sig-windows | prow label plugin | |
status/in-progress |
TODO this is the mungegithub milestone-maintainer munger or prow milestonestatus plugin, and I'm not sure I understand what it's current usage is vs. its intended usage | prow milestonestatus plugin | |
status/in-review |
TODO this is the mungegithub milestone-maintainer munger or prow milestonestatus plugin, and I'm not sure I understand what it's current usage is vs. its intended usage | prow milestonestatus plugin |
| Name | Description | Added By | Notes |
|---|---|---|---|
help wanted |
denotes that an issue or PR is ready for contributor according to the [help-wanted] guidelines, applied in response to /help by the help prow plugin | prow help plugin | was previously "help-wanted", "for-new-contributors", |
needs-sig |
applied to issues by the prow plugin "requiresig" when there are no SIG labels | prow requiresig plugin |
| Name | Description | Added By | Notes |
|---|---|---|---|
approved |
comes from the prow approval plugin | prow approve plugin | |
cherrypick-approved |
TODO This appears to be consumed by the cherrypick-queue munger, it is mostly added by release branch manager humans to signify their final stamp of approval. It can be added by the cherrypick-auto-approve munger, but we don't appear to rely on it so much | humans | |
cherrypick-candidate |
TODO This looks like it's manually applied to PRs to master that should be considered for cherry-pick into a release branch, and is somehow consumed by the mungegithub cherrypick-queue | humans | |
cla: human-approved |
DEPRECATED. This is a holdover from when we had difficulties getting either the google or cncf CLA bots to behave. It can only be manually applied and is consumed by the submit-queue. It has seen very little use lately. | humans | |
cla: no |
REMOVING. This was what we used when the googlebot was enforcing CLA. We now use the cncf-cla labels. | googlebot | will be deleted after 2018-03-16 00:00:00 +0000 UTC |
cla: yes |
REMOVING. This was what we used when the googlebot was enforcing CLA. We now use the cncf-cla labels. | googlebot | will be deleted after 2018-03-16 00:00:00 +0000 UTC |
cncf-cla: no |
applied by the prow cla plugin to PR's if the CNCF CLA bot reports that the PR author has not signed the CNCF CLA | prow cla plugin | |
cncf-cla: yes |
applied by the prow cla plugin to PR's if the CNCF CLA bot reports that the PR author has signed the CNCF CLA | prow cla plugin | |
do-not-merge |
DEPRECATED. This denotes that a PR should not be merged, we would like to deprecate / dissuade further usage as it can only be manually applied/removed. | humans | |
do-not-merge/blocked-paths |
applied by the prow blockade plugin, denotes that a PR should not be merged because it touches files in blocked paths | prow blockade plugin | |
do-not-merge/cherry-pick-not-approved |
TODO denotes that a PR should not be merged into a release branch because the cherrypick-approved label is not present, what applies it? | mungegithub cherrypick-label-unapproved munger | |
do-not-merge/hold |
denotes that a PR should not be merged because someone has issued a /hold command, applied by the prow hold pluigin | prow hold plugin | |
do-not-merge/release-note-label-needed |
denotes that a PR should not be merged because a release note is needed in the PR description | prow releasenote plugin | |
do-not-merge/work-in-progress |
denotes that a PR should not be merged because it is a work in progress, based on the presence of a '[wip]' prefix in the PR title | prow wip plugin | |
lgtm |
PR is ready to be merged | prow lgtm plugin | |
needs-ok-to-test |
TBD auto applied to PRs by what? can be removed by a /needs-ok-to-test | trigger | |
needs-rebase |
applied to PRs by mungegithub when they have merge conflicts with HEAD | TBD | |
ok-to-merge |
REMOVING. This is unused. | humans | will be deleted after 2018-03-16 00:00:00 +0000 UTC |
queue/blocks-others |
DEPRECATED. This is only effective on kubernetes/kubernetes, and should go away once we stop using the submit-queue. Manually applied to bump a PR up the queue. | humans | |
queue/critical-fix |
DEPRECATED. This is only effective on kubernetes/kubernetes, and should go away once we stop using the submit-queue. Manually applied to bump a PR up the queue. | humans | |
queue/fix |
DEPRECATED. This is only effective on kubernetes/kubernetes, and should go away once we stop using the submit-queue. Manually applied to bump a PR up the queue. | humans | |
queue/multiple-rebases |
DEPRECATED. This is only effective on kubernetes/kubernetes, and should go away once we stop using the submit-queue. Manually applied to bump a PR up the queue. | humans | |
release-note |
TODO unsure how specifically this is used | prow releasenote plugin | |
release-note-action-required |
TODO unsure how specifically this is ued | prow releasenote plugin | |
release-note-label-needed |
DEPRECATED. This should be removed/migrated to do-not-merge/release-note-label-needed. | humans | |
release-note-none |
TBD | prow releasenote plugin | |
retest-not-required |
TODO this is manually applied and only submit-queue pays attention to it, so I'm not sure what this means for tide and k/k | humans | |
retest-not-required-docs-only |
TODO this is auto applied by the prow docs-no-retest plugin, but only the submit-queue pays attention to it, so I'm not sure what this means for tide and k/k | prow docs-no-retest plugin | |
size/L |
applied to PR's that change 100-499 lines (ignoring generated files) by the prow plugin "size" | prow size plugin | |
size/M |
applied to PR's that change 30-99 lines (ignoring generated files) by the prow plugin "size" | prow size plugin | |
size/S |
applied to PR's that change 10-29 lines (ignoring generated files) by the prow plugin "size" | prow size plugin | |
size/XL |
applied to PR's that change 500-999 lines (ignoring generated files) by the prow plugin "size" | prow size plugin | |
size/XS |
applied to PR's that change 0-9 lines (ignoring generated files) by the prow plugin "size" | prow size plugin | |
size/XXL |
applied to PR's that change 1000+ lines (ignoring generated files) by the prow plugin "size" | prow size plugin |