Skip to content

No labels!

There aren’t any labels for this repository quite yet.

146 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
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
area/prow
area/prow
Setting up or working with prow in general, prow.k8s.io, prow build clusters
10
area/registry.k8s.io
area/registry.k8s.io
Code in registry.k8s.io/
3
area/release-eng
area/release-eng
Issues or PRs related to the Release Engineering subproject
16
area/terraform
area/terraform
Terraform modules, testing them, writing more of them, code in infra/gcp/clusters/
3
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.
20
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.
1
committee/steering
committee/steering
Denotes an issue or PR intended to be handled by the steering committee.
2
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.
4
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.
1
do-not-merge
do-not-merge
DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
1
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
3
kind/api-change
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
1
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
6
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
12
kind/deprecation
kind/deprecation
Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
1
kind/design
kind/design
Categorizes issue or PR as related to design.