Skip to content

No labels!

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

80 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
acknowledge-critical-fixes-only
acknowledge-critical-fixes-only
Indicates if the issuer of the label is OK with the policy.
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.
1
area/dependency
area/dependency
Issues or PRs related to dependency changes
area/licensing
area/licensing
Issues or PRs related to Kubernetes licensing
backport-risk-assessed
backport-risk-assessed
Indicates a PR to a release branch has been evaluated and considered safe to accept.
backports/unvalidated-commits
backports/unvalidated-commits
Indicates that not all commits come to merged upstream PRs.
backports/validated-commits
backports/validated-commits
Indicates that all commits come to merged upstream PRs.
bugzilla/invalid-bug
bugzilla/invalid-bug
Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting.
bugzilla/severity-high
bugzilla/severity-high
Referenced Bugzilla bug's severity is high for the branch this PR is targeting.
bugzilla/severity-low
bugzilla/severity-low
Referenced Bugzilla bug's severity is low for the branch this PR is targeting.
bugzilla/severity-medium
bugzilla/severity-medium
Referenced Bugzilla bug's severity is medium for the branch this PR is targeting.
bugzilla/severity-unspecified
bugzilla/severity-unspecified
Referenced Bugzilla bug's severity is unspecified for the PR.
bugzilla/severity-urgent
bugzilla/severity-urgent
Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting.
bugzilla/valid-bug
bugzilla/valid-bug
Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting.
cherry-pick-approved
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
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/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
1
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.
do-not-merge
do-not-merge
DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.
docs-approved
docs-approved
Signifies that Docs has signed off on this PR
documentation
documentation
Improvements or additions to documentation
go
go
Pull requests that update Go code
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
jira/invalid-bug
jira/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.