jetstack-bot

Results 1795 comments of jetstack-bot

Wrong nameserver for vault clusterissuer

Stale issues rot after 30d of inactivity. Mark the issue as fresh with `/remove-lifecycle rotten`. Rotten issues close after an additional 30d of inactivity. If this issue is safe to...

Allowing skipping HTTP01 and DNS01 self-check on a per-solver basis

@munnerz: This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed [here](https://git.k8s.io/community/contributors/guide/help-wanted.md). If this request no longer meets these requirements, the...

Create 20220720-per-certificate-owner-ref.md

[APPROVALNOTIFIER] This PR is **APPROVED** This pull-request has been approved by: *maelvls* The full list of commands accepted by this bot can be found [here](https://go.k8s.io/bot-commands?repo=cert-manager%2Fcert-manager). The pull request process is...

Document a security issue reporting, response, and distribution process

Issues go stale after 90d of inactivity. Mark the issue as fresh with `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue...

Document a security issue reporting, response, and distribution process

Issues go stale after 90d of inactivity. Mark the issue as fresh with `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue...

Document a security issue reporting, response, and distribution process

Issues go stale after 90d of inactivity. Mark the issue as fresh with `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue...

Document a security issue reporting, response, and distribution process

Stale issues rot after 30d of inactivity. Mark the issue as fresh with `/remove-lifecycle rotten`. Rotten issues close after an additional 30d of inactivity. If this issue is safe to...

Document a security issue reporting, response, and distribution process

Issues go stale after 90d of inactivity. Mark the issue as fresh with `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue...

Document a security issue reporting, response, and distribution process

Stale issues rot after 30d of inactivity. Mark the issue as fresh with `/remove-lifecycle rotten`. Rotten issues close after an additional 30d of inactivity. If this issue is safe to...

ACME Issuer should support option to write intermediate and root CAs to Ingress TLS secret

Issues go stale after 90d of inactivity. Mark the issue as fresh with `/remove-lifecycle stale`. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue...