Skip to content

No labels!

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

136 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
api-review
api-review
Categorizes an issue or PR as actively needing an API review.
approved
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
9
area/community-meeting
area/community-meeting
Issues or PRs that should potentially be discussed in a Kubernetes community meeting.
area/dependency
area/dependency
Issues or PRs related to dependency changes
area/provider/aws
area/provider/aws
Issues or PRs related to aws provider
area/provider/azure
area/provider/azure
Issues or PRs related to azure provider
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
beginner
beginner
cherry-pick-approved
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
ci-extended
ci-extended
Run additional tests
ci-full
ci-full
Run every available tests
ci-short
ci-short
Run a quick CI pipeline
ci-triggered
ci-triggered
cncf-cla: no
cncf-cla: no
Indicates the PR's author has not signed the CNCF CLA.
4
cncf-cla: yes
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
30
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.
committee/steering
committee/steering
Denotes an issue or PR intended to be handled by the steering committee.
compat
compat
dependencies
dependencies
Pull requests that update a dependency file
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/contains-merge-commits
do-not-merge/contains-merge-commits
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.