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.

area/community-meeting

Issues or PRs that should potentially be discussed in a Kubernetes community meeting.

area/dependency

Issues or PRs related to dependency changes

area/provider/aws

Issues or PRs related to aws provider

area/provider/azure

Issues or PRs related to azure provider

area/provider/digitalocean

Issues or PRs related to digitalocean provider

area/provider/gcp

Issues or PRs related to gcp provider

area/provider/ibmcloud

Issues or PRs related to ibmcloud provider

area/provider/openstack

Issues or PRs related to openstack provider

area/provider/vmware

Issues or PRs related to vmware provider

cherry-pick-approved

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.

committee/code-of-conduct

Denotes an issue or PR intended to be handled by the code of conduct committee.

committee/security-response

Denotes an issue or PR intended to be handled by the product security committee.

committee/steering

Denotes an issue or PR intended to be handled by the steering committee.

Pull requests that update a dependency file

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

Indicates that a PR is not yet approved to merge into a release branch.

do-not-merge/hold

Indicates that a PR should not merge because someone has issued a /hold command.

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

Indicates that a PR should not merge because it has an invalid OWNERS file in it.

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

Indicates that a PR should not merge because it is a work in progress.

DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.

Pull requests that update GitHub Actions code

Pull requests that update Go code

good first issue

Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Pull requests that update Javascript code

kind/api-change

Categorizes issue or PR as related to adding, removing, or otherwise changing an API

Categorizes issue or PR as related to a bug.

Categorizes issue or PR as related to cleaning up code, process, or technical debt.

kind/deprecation

Categorizes issue or PR as related to a feature/enhancement marked for deprecation.

Categorizes issue or PR as related to design.

kind/documentation

Categorizes issue or PR as related to documentation.

kind/failing-test

Categorizes issue or PR as related to a consistently or frequently failing test.

Categorizes issue or PR as related to a new feature.

Categorizes issue or PR as related to a flaky test.

Categorize issue or PR as related to i18n.

kind/regression

Categorizes issue or PR as related to a regression from a prior release.

Categorizes issue or PR as a support question.

Updates or issues for German translations.

Updates or issues for French translations.

Updates or issues for Japanese translations.

Updates or issues for Korean translations.

Updates or issues for Chinese translations.

"Looks good to me", indicates that a PR is ready to be merged.

lifecycle/active

Indicates that an issue or PR is actively being worked on by a contributor.

lifecycle/frozen

Indicates that an issue or PR should not be auto-closed due to staleness.

lifecycle/rotten

Denotes an issue or PR that has aged beyond stale and will be auto-closed.

lifecycle/stale

Denotes an issue or PR has remained open with no activity and has become stale.

Indicates a PR lacks a `kind/foo` label and requires one.

needs-ok-to-test

Indicates a PR that requires an org member to verify it is safe to test.

Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Indicates an issue or PR lacks a `sig/foo` label and requires one.

Indicates an issue or PR lacks a `triage/foo` label and requires one.

Indicates a non-member PR verified by an org member that is safe to test.

priority/awaiting-more-evidence

Lowest priority. Possibly useful, but not yet enough support to actually get it done.

priority/backlog

Higher priority than priority/awaiting-more-evidence.

priority/critical-urgent

Highest priority. Must be actively worked on as someone's top priority right now.

priority/important-longterm

Important over the long term, but may not be staffed and/or may need multiple releases to complete.

priority/important-soon

Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Denotes a PR that will be considered when it comes time to generate release notes.

release-note-action-required

Denotes a PR that introduces potentially breaking changes that require user action.

release-note-none

Denotes a PR that doesn't merit a release note.

sig/api-machinery

Categorizes an issue or PR as relevant to SIG API Machinery.

Categorizes an issue or PR as relevant to SIG Apps.

sig/architecture

Categorizes an issue or PR as relevant to SIG Architecture.

Categorizes an issue or PR as relevant to SIG Auth.

sig/autoscaling

Categorizes an issue or PR as relevant to SIG Autoscaling.

Categorizes an issue or PR as relevant to SIG CLI.

sig/cloud-provider

Categorizes an issue or PR as relevant to SIG Cloud Provider.

sig/cluster-lifecycle

Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.

sig/contributor-experience

Categorizes an issue or PR as relevant to SIG Contributor Experience.

Categorizes an issue or PR as relevant to SIG Docs.

Categorizes an issue or PR as relevant to SIG Etcd.

sig/instrumentation

Categorizes an issue or PR as relevant to SIG Instrumentation.

Categorizes an issue or PR as relevant to SIG K8s Infra.

sig/multicluster

Categorizes an issue or PR as relevant to SIG Multicluster.

Categorizes an issue or PR as relevant to SIG Network.

Categorizes an issue or PR as relevant to SIG Node.

Categorizes an issue or PR as relevant to SIG Release.

sig/scalability

Categorizes an issue or PR as relevant to SIG Scalability.

Categorizes an issue or PR as relevant to SIG Scheduling.

Categorizes an issue or PR as relevant to SIG Security.

sig/service-catalog

Categorizes an issue or PR as relevant to SIG Service Catalog.

Categorizes an issue or PR as relevant to SIG Storage.

Categorizes an issue or PR as relevant to SIG Testing.

Categorizes an issue or PR as relevant to SIG UI.

Categorizes an issue or PR as relevant to SIG Usability.

Categorizes an issue or PR as relevant to SIG Windows.

Denotes a PR that changes 100-499 lines, ignoring generated files.

Denotes a PR that changes 30-99 lines, ignoring generated files.

Denotes a PR that changes 10-29 lines, ignoring generated files.

Denotes a PR that changes 500-999 lines, ignoring generated files.

Denotes a PR that changes 0-9 lines, ignoring generated files.

Denotes a PR that changes 1000+ lines, ignoring generated files.

tide/merge-blocker

Denotes an issue that blocks the tide merge queue for a branch while it is open.

tide/merge-method-merge

Denotes a PR that should use a standard merge by tide when it merges.

tide/merge-method-rebase

Denotes a PR that should be rebased by tide when it merges.

tide/merge-method-squash

Denotes a PR that should be squashed by tide when it merges.

triage/accepted

Indicates an issue or PR is ready to be actively worked on.

triage/duplicate

Indicates an issue is a duplicate of other open issue.

triage/needs-information

Indicates an issue needs more information in order to work on it.

triage/not-reproducible

Indicates an issue can not be reproduced as described.

triage/unresolved

Indicates an issue that can not or will not be resolved.

Categorizes an issue or PR as relevant to ug-big-data.

Categorizes an issue or PR as relevant to ug-vmware.

wg/api-expression

Categorizes an issue or PR as relevant to WG API Expression.

Categorizes an issue or PR as relevant to WG Batch.

Categorizes an issue or PR as relevant to wg-cluster-api.

wg/component-standard

Categorizes an issue or PR as relevant to WG Component Standard.

wg/data-protection

Categorizes an issue or PR as relevant to WG Data Protection.

wg/device-management

Categorizes an issue or PR as relevant to WG Device Management.

Categorizes an issue or PR as relevant to WG IOT Edge.

Categorizes an issue or PR as relevant to WG LTS.

wg/machine-learning

Categorizes an issue or PR as relevant to WG Machine Learning.

wg/multitenancy

Categorizes an issue or PR as relevant to WG Multitenancy.

Categorizes an issue or PR as relevant to WG Naming.

Categorizes an issue or PR as relevant to WG Policy.

Categorizes an issue or PR as relevant to WG Reliability

wg/security-audit

Categorizes an issue or PR as relevant to WG Security Audit.

Categorizes an issue or PR as relevant to WG Serving.

wg/structured-logging

Categorizes an issue or PR as relevant to WG Structured Logging.

¯\\\_(ツ)_/¯

No labels found. Sorry about that.