Labels
Labels
134 labels
- Categorizes an issue or PR as actively needing an API review.
- Indicates a PR has been approved by an approver from all required OWNERS files.
- Issues or PRs related to kubernetes code organization
- Issues or PRs that should potentially be discussed in a Kubernetes community meeting.
- Issues or PRs related to the upstream marketing team
- Issues or PRs related to dependency changes
- Issues or PRs related to the Enhancements subproject
- Issues or PRs related to aws provider
- Issues or PRs related to azure provider
- Issues or PRs related to digitalocean provider
- Issues or PRs related to gcp provider
- Issues or PRs related to ibmcloud provider
- Issues or PRs related to openstack provider
- Issues or PRs related to vmware provider
- Issues or PRs related to the Release Engineering subproject
- Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
- Indicates the PR's author has not signed the CNCF CLA.
- Indicates the PR's author has signed the CNCF CLA.
- Denotes an issue or PR intended to be handled by the code of conduct committee.
- Denotes an issue or PR intended to be handled by the product security committee.
- Denotes an issue or PR intended to be handled by the steering committee.
- DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.
- Indicates that a PR should not merge because it touches files in blocked paths.
- Indicates that a PR is not yet approved to merge into a release branch.
- Indicates that a PR should not merge because someone has issued a /hold command.
- Indicates that a PR should not merge because it has an invalid commit message.
- Indicates that a PR should not merge because it has an invalid OWNERS file in it.