Skip to content

No labels!

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

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.
area/api
area/api
Indicates an issue or PR that deals with the API.
area/automation
area/automation
Issues that are related to automation aspects of the website or other projects.
area/dependency
area/dependency
Issues or PRs related to dependency changes
area/dogfooding
area/dogfooding
Indicates an issue on dogfooding (aka using Pipeline to test Pipeline)
area/ecosystem
area/ecosystem
Issues that are related to CI/CD ecosystem
area/entrypoint
area/entrypoint
area/epic
area/epic
Issues that should be considered as Epics (aka multiple sub-tasks, …)
area/licensing
area/licensing
Issues or PRs related to Kubernetes licensing
area/metrics
area/metrics
Issues related to metrics
area/performance
area/performance
Issues or PRs that are related to performance aspects.
area/plumbing
area/plumbing
Issues or PRs related to the plumbing infrastructure but needing attention in a non-plumbing repo.
area/release
area/release
Indicates an issue on release (process, tasks).
area/resolution
area/resolution
Issues related to remote resolution
area/roadmap
area/roadmap
Issues that are part of the project (or organization) roadmap (usually an epic)
area/s3c
area/s3c
Issues or PRs that are related to Secure Software Supply Chain (S3C)
area/test-infra
area/test-infra
Issues or PRs related to the testing infrastructure
area/testing
area/testing
Issues or PRs related to testing
area/user-study
area/user-study
area/yamls
area/yamls
This issue involves writing a lot of yaml
cla: no
cla: no
cla: yes
cla: yes
Trying to make the CLA bot happy with ppl from different companies work on one commit
cncf-cla: no
cncf-cla: no
Indicates the PR's author has not signed the CNCF CLA.
cncf-cla: yes
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
dependencies
dependencies
Used by dependabot - identifies all PRs created by dependabot
design
design
This task is about creating and discussing a design
do-not-merge/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
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.