Unlabeled
api-review
Categorizes an issue or PR as actively needing an API review.
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
area/admin
Indicates an issue on admin area.
area/admission-control
area/api
Indicates an issue on api area.
area/apiserver
area/app-lifecycle
area/artifacts
Issues or PRs related to the hosting of release artifacts for subprojects
area/audit
area/batch
area/build-release
area/cadvisor
area/client-libraries
area/cloudprovider
area/code-generation
area/code-organization
Issues or PRs related to kubernetes code organization
area/community-meeting
Issues or PRs that should potentially be discussed in a Kubernetes community meeting.
area/configmap-api
area/conformance
Issues or PRs related to kubernetes conformance tests
area/controller-manager
area/custom-resources
area/declarative-configuration
area/deflake
Issues or PRs related to deflaking kubernetes tests
area/dependency
Issues or PRs related to dependency changes
area/dns
area/docker
area/downward-api
area/e2e-test-framework
Issues or PRs related to refactoring the kubernetes e2e test framework
area/ecosystem
area/etcd
area/example/cassandra
area/example
area/extensibility
area/federation
area/HA
area/hw-accelerators
area/images-registry
area/ingress
area/introspection
area/ipv6
area/ipvs
area/isolation
area/kube-proxy
area/kubeadm
area/kubectl
area/kubelet
area/kubelet-api
area/logging
area/monitoring
area/network-policy
Issues or PRs related to Network Policy subproject
area/node-e2e
area/node-lifecycle
area/nodecontroller
area/os/coreos
area/os/fedora
area/os/ubuntu
area/platform/gce
area/platform/mesos
area/platform/vagrant
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
area/release-eng
Issues or PRs related to the Release Engineering subproject
area/reliability
area/rkt
area/secret-api
area/security
area/stable-metrics
Issues or PRs involving stable metrics
area/stateful-apps
area/swagger
area/system-requirement
area/teardown
area/test
area/test-infra
area/ui
area/upgrade
area/usability
area/workload-api/cronjob
area/workload-api/daemonset
area/workload-api/deployment
area/workload-api/job
area/workload-api/replicaset
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
cncf-cla: no
Indicates the PR's author has not signed the CNCF CLA.
cncf-cla: yes
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.
dependencies
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/contains-merge-commits
Indicates a PR which contains merge commits.
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/needs-kind
Indicates a PR lacks a `kind/foo` label and requires one.
do-not-merge/needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
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.
do-not-merge
DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed.
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/bug
Categorizes issue or PR as related to a bug.
kind/cleanup
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.
kind/design
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.
kind/feature
Categorizes issue or PR as related to a new feature.
kind/flake
Categorizes issue or PR as related to a flaky test.
kind/regression
Categorizes issue or PR as related to a regression from a prior release.
kind/support
Categorizes issue or PR as a support question.
lgtm
"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.
milestone/incomplete-labels
milestone/needs-approval
milestone/needs-attention
milestone/removed
needs-kind
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.
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
official-cve-feed
Issues or PRs related to CVEs officially announced by Security Response Committee (SRC)
ok-to-test
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.
release-blocker
release-note
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.
sig/apps
Categorizes an issue or PR as relevant to SIG Apps.
sig/architecture
Categorizes an issue or PR as relevant to SIG Architecture.
sig/auth
Categorizes an issue or PR as relevant to SIG Auth.
sig/autoscaling
Categorizes an issue or PR as relevant to SIG Autoscaling.
sig/cli
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.
sig/docs
Categorizes an issue or PR as relevant to SIG Docs.
sig/etcd
Categorizes an issue or PR as relevant to SIG Etcd.
sig/instrumentation
Categorizes an issue or PR as relevant to SIG Instrumentation.
sig/k8s-infra
Categorizes an issue or PR as relevant to SIG K8s Infra.
sig/multicluster
Categorizes an issue or PR as relevant to SIG Multicluster.
sig/network
Categorizes an issue or PR as relevant to SIG Network.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
sig/scalability
Categorizes an issue or PR as relevant to SIG Scalability.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
sig/security
Categorizes an issue or PR as relevant to SIG Security.
sig/service-catalog
Categorizes an issue or PR as relevant to SIG Service Catalog.
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
sig/ui
Categorizes an issue or PR as relevant to SIG UI.
sig/usability
Categorizes an issue or PR as relevant to SIG Usability.
sig/windows
Categorizes an issue or PR as relevant to SIG Windows.
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
size/XL
Denotes a PR that changes 500-999 lines, ignoring generated files.
size/XS
Denotes a PR that changes 0-9 lines, ignoring generated files.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
status/approved-for-milestone
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.
ug/big-data
Categorizes an issue or PR as relevant to ug-big-data.
ug/vmware
Categorizes an issue or PR as relevant to ug-vmware.
wg/api-expression
Categorizes an issue or PR as relevant to WG API Expression.
wg/batch
Categorizes an issue or PR as relevant to WG Batch.
wg/cluster-api
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/iot-edge
Categorizes an issue or PR as relevant to WG IOT Edge.
wg/lts
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.
wg/naming
Categorizes an issue or PR as relevant to WG Naming.
wg/policy
Categorizes an issue or PR as relevant to WG Policy.
wg/reliability
Categorizes an issue or PR as relevant to WG Reliability
wg/security-audit
Categorizes an issue or PR as relevant to WG Security Audit.
wg/structured-logging
Categorizes an issue or PR as relevant to WG Structured Logging.
¯\_(ツ)_/¯
¯\\\_(ツ)_/¯
No labels found. Sorry about that.