Skip to content

No labels!

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

206 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
area/reliability
area/reliability
Issues or PRs related to system reliability
area/rkt
area/rkt
Issues or PRs related to rkt (a pod-native container engine)
area/secret-api
area/secret-api
Issues or PRs related to Secret API
area/security
area/security
Issues or PRs related to security features or vulnerabilities
area/stateful-apps
area/stateful-apps
Issues or PRs related to stateful applications
area/swagger
area/swagger
Issues or PRs related to Swagger API documentation
area/system-requirement
area/system-requirement
Issues or PRs related to system requirements
area/teardown
area/teardown
Issues or PRs related to system teardown or cleanup
area/test
area/test
Issues or PRs related to tests or testing infrastructure
area/test-infra
area/test-infra
Issues or PRs related to test infrastructure
area/ui
area/ui
Issues or PRs related to user interface
area/upgrade
area/upgrade
Issues or PRs related to system upgrades
area/usability
area/usability
Issues or PRs related to usability improvements or concerns
area/workload-api/cronjob
area/workload-api/cronjob
Issues or PRs related to workload API's cronjob features
area/workload-api/daemonset
area/workload-api/daemonset
Issues or PRs related to workload API's daemonset features
area/workload-api/deployment
area/workload-api/deployment
Issues or PRs related to workload API's deployment features
area/workload-api/job
area/workload-api/job
Issues or PRs related to workload API's job features
cherry-pick-approved
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
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.
committee/code-of-conduct
committee/code-of-conduct
Denotes an issue or PR intended to be handled by the code of conduct committee.
committee/security-response
committee/security-response
Denotes an issue or PR intended to be handled by the product security committee.
committee/steering
committee/steering
Denotes an issue or PR intended to be handled by the steering committee.
dependencies
dependencies
Pull requests that update a dependency file
2
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/contains-merge-commits
do-not-merge/contains-merge-commits
Indicates a PR which contains merge commits.
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-commit-message
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
do-not-merge/invalid-owners-file
Indicates that a PR should not merge because it has an invalid OWNERS file in it.