Skip to content

No labels!

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

76 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
approved
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
area/acme/dns01
area/acme/dns01
Indicates a PR modifies ACME DNS01 provider code
11
area/acme/http01
area/acme/http01
Indicates a PR modifies ACME HTTP01 provider code
3
area/acme
area/acme
Indicates a PR directly modifies the ACME Issuer code
23
area/api
area/api
Indicates a PR directly modifies the 'pkg/apis' directory
17
area/ca
area/ca
Indicates a PR directly modifies the CA Issuer code
3
area/cainjector
area/cainjector
Indicates a PR or issue relates to the cainjector component
area/ctl
area/ctl
Indicates a PR or issue relates to the cert-manager-ctl CLI component
area/deploy
area/deploy
Indicates a PR modifies deployment configuration
31
area/gateway-shim
area/gateway-shim
Indicates a PR or issue relates to the gateway-shim feature (as in Gateway API).
1
area/ingress-shim
area/ingress-shim
Indicates a PR or issue relates to the ingress-shim 'auto-certificate' component
area/monitoring
area/monitoring
Indicates a PR or issue relates to monitoring
1
area/testing
area/testing
Issues relating to testing
15
area/vault
area/vault
Indicates a PR directly modifies the Vault Issuer code
2
area/venafi
area/venafi
Indicates a PR directly modifies the Venafi Issuer code
1
area/webhook
area/webhook
Indicates a PR or issue relates to the webhook component
cherry-pick-approved
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager
cherrypick-candidate
cherrypick-candidate
Denotes a PR to master as a candidate for cherry picking into a release branch.
dco-signoff: no
dco-signoff: no
Indicates that at least one commit in this pull request is missing the DCO sign-off message.
1
dco-signoff: yes
dco-signoff: yes
Indicates that all commits in the pull request have the valid DCO sign-off message.
54
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.
4
do-not-merge/invalid-owners-file
do-not-merge/invalid-owners-file
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.
3
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.
6
Epic
Epic
Indicates an issues that is meant for tracking a collection of other issues.
flake/test-logic
flake/test-logic
Indicates that the issue relates to test flakes caused by incorrect logic inside a test
flake/test-setup
flake/test-setup
Indicates that the issue relates to test flakes when setting up a test environment