Graduate DefaultPrivateKeyRotationPolicyAlways to GA and remove gating by wallrj-cyberark · Pull Request #8287 · cert-manager/cert-manager

wallrj-cyberark · 2025-12-02T16:05:56Z

The default private key rotation policy was changed to Always in #7723 and released in v1.18.0, in June 2025.
The change was introduced behind a Beta feature-gate (on-by-default) as an escape hatch for users who were not ready to adopt the new default and Helm chart and API warnings were added, to alert everyone to the new behaviour.

Now, I propose we graduate the feature gate to GA for the February 2026 release of cert-manager 1.20 and remove the warnings.
Users will have had two releases and 8 months to adapt to the new default.

The feature-gate DefaultPrivateKeyRotationPolicyAlways moved from Beta to GA and can no longer be disabled.

/kind cleanup

Changes

Graduate DefaultPrivateKeyRotationPolicyAlways to GA and remove gating
Make runtime default RotationPolicy Always (no feature gate)
Remove user-facing warnings and feature-gate docs from CRDs and notes
Update tests and generated OpenAPI to match the new default

Testing

kind create cluster
export KO_REGISTRY=ttl.sh/$(uuidgen)/cert-manager
make ko-deploy-certmanager

https://cert-manager.io/docs/installation/kubectl/#2-optional-end-to-end-verify-the-installation

cat <<EOF > test-resources.yaml
apiVersion: v1
kind: Namespace
metadata:
  name: cert-manager-test
---
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: test-selfsigned
  namespace: cert-manager-test
spec:
  selfSigned: {}
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: selfsigned-cert
  namespace: cert-manager-test
spec:
  dnsNames:
    - example.com
  secretName: selfsigned-cert-tls
  issuerRef:
    name: test-selfsigned
EOF

Renew the cert and observe the default rotation of the private key

$ cmctl renew -n cert-manager-test --all
Manually triggered issuance of Certificate cert-manager-test/selfsigned-cert

$ kubectl get events -n cert-manager-test -w 

...
0s          Normal    Generated            certificate/selfsigned-cert            Stored new private key in temporary Secret resource "selfsigned-cert-sjszq"
0s          Normal    WaitingForApproval   certificaterequest/selfsigned-cert-2   Not signing CertificateRequest until it is Approved
0s          Normal    WaitingForApproval   certificaterequest/selfsigned-cert-2   Not signing CertificateRequest until it is Approved
0s          Normal    Requested            certificate/selfsigned-cert            Created new CertificateRequest resource "selfsigned-cert-2"
0s          Normal    WaitingForApproval   certificaterequest/selfsigned-cert-2   Not signing CertificateRequest until it is Approved
0s          Normal    WaitingForApproval   certificaterequest/selfsigned-cert-2   Not signing CertificateRequest until it is Approved
0s          Normal    WaitingForApproval   certificaterequest/selfsigned-cert-2   Not signing CertificateRequest until it is Approved
0s          Normal    cert-manager.io      certificaterequest/selfsigned-cert-2   Certificate request has been approved by cert-manager.io
0s          Warning   BadConfig            certificaterequest/selfsigned-cert-2   Certificate will be issued with an empty Issuer DN, which contravenes RFC 5280 and could break some strict clients
0s          Normal    CertificateIssued    certificaterequest/selfsigned-cert-2   Certificate fetched from issuer successfully
0s          Normal    Issuing              certificate/selfsigned-cert            The certificate has been successfully issued

Patch the cert with rotationPolicy: Never and observe the private key being re-used.

$ kubectl patch certificate -n cert-manager-test selfsigned-cert --type=merge --patch='{"spec": {"privateKey": {"rotationPolicy": "Never
"}}}'
certificate.cert-manager.io/selfsigned-cert patched

$ cmctl renew -n cert-manager-test --all
Manually triggered issuance of Certificate cert-manager-test/selfsigned-cert

$ kubectl get events -n cert-manager-test -w 
...
l0s          Normal    Reused               certificate/selfsigned-cert            Reusing private key stored in existing Secret resource "selfsigned-cert-tls"
0s          Normal    Requested            certificate/selfsigned-cert            Created new CertificateRequest resource "selfsigned-cert-3"
0s          Normal    WaitingForApproval   certificaterequest/selfsigned-cert-3   Not signing CertificateRequest until it is Approved
0s          Normal    WaitingForApproval   certificaterequest/selfsigned-cert-3   Not signing CertificateRequest until it is Approved
0s          Normal    WaitingForApproval   certificaterequest/selfsigned-cert-3   Not signing CertificateRequest until it is Approved
0s          Normal    WaitingForApproval   certificaterequest/selfsigned-cert-3   Not signing CertificateRequest until it is Approved
0s          Normal    WaitingForApproval   certificaterequest/selfsigned-cert-3   Not signing CertificateRequest until it is Approved
0s          Normal    cert-manager.io      certificaterequest/selfsigned-cert-3   Certificate request has been approved by cert-manager.io
0s          Warning   BadConfig            certificaterequest/selfsigned-cert-3   Certificate will be issued with an empty Issuer DN, which contravenes RFC 5280 and could break some strict clients
0s          Normal    CertificateIssued    certificaterequest/selfsigned-cert-3   Certificate fetched from issuer successfully
0s          Normal    Issuing              certificate/selfsigned-cert            The certificate has been successfully issued

CyberArk tracker: VC-47365

- Graduate DefaultPrivateKeyRotationPolicyAlways to GA and remove gating - Make runtime default RotationPolicy Always (no feature gate) - Remove user-facing warnings and feature-gate docs from CRDs and notes - Update tests and generated OpenAPI to match the new default Signed-off-by: Richard Wall <richard.wall@cyberark.com>

wallrj-cyberark · 2025-12-02T16:17:25Z

deploy/charts/cert-manager/templates/NOTES.txt

-The default private key rotation policy for Certificate resources was
-changed to `Always` in cert-manager >= v1.18.0.
-Learn more in the [1.18 release notes](https://cert-manager.io/docs/releases/release-notes/release-notes-1.18).
-


The private key rotation warning has been removed, but other warnings still work.

$ make helm-chart ... $ helm install --dry-run test _bin/cert-manager-v1.20.0-alpha.0-102-gbd8a9dadaded52.tgz --set installCRDs=true ... NOTES: ⚠️ WARNING: `installCRDs` is deprecated, use `crds.enabled` instead. cert-manager v1.20.0-alpha.0-102-gbd8a9dadaded52 has been deployed successfully! In order to begin issuing certificates, you will need to set up a ClusterIssuer or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer). More information on the different types of issuers and how to configure them can be found in our documentation: https://cert-manager.io/docs/configuration/ For information on how to configure cert-manager to automatically provision Certificates for Ingress resources, take a look at the `ingress-shim` documentation: https://cert-manager.io/docs/usage/ingress/

wallrj-cyberark · 2025-12-02T16:18:49Z

deploy/charts/cert-manager/templates/crd-cert-manager.io_certificates.yaml

auto-generated

wallrj-cyberark · 2025-12-02T16:19:05Z

deploy/crds/cert-manager.io_certificates.yaml

auto-generated

wallrj-cyberark · 2025-12-02T16:21:19Z

internal/apis/certmanager/v1/defaults.go

 //
-// TODO(wallrj): When DefaultPrivateKeyRotationPolicyAlways is GA, the default
-// value can probably be added as an API default by adding:
+// TODO(wallrj): Use an API default when we have them implemented, by adding:
 //
 //	`// +default="Always"`
 //


Contrary to what I wrote in the original TODO, we still don't use any API defaults.
We tried to introduce them in 1.19, but then reverted the change.
Read more in the 1.19.1 release notes.

wallrj-cyberark · 2025-12-02T16:26:52Z

internal/generated/openapi/zz_generated.openapi.go

auto-generated

wallrj-cyberark · 2025-12-02T16:35:39Z

deploy/charts/cert-manager/values.schema.json

auto-generated

wallrj-cyberark · 2025-12-02T16:36:19Z

deploy/charts/cert-manager/README.template.md

auto-generated

wallrj-cyberark · 2025-12-02T16:37:28Z

deploy/charts/cert-manager/values.yaml

 #    numberOfConcurrentWorkers: 200
 #    enableGatewayAPI: true
-#    # Feature gates as of v1.18.1. Listed with their default values.
+#    # Feature gates as of v1.20.0. Listed with their default values.


These example config lines hadn't been updated in a while, so I removed some other features which are also GA or which were withdrawn before they graduated to Beta.

wallrj-cyberark · 2025-12-02T16:41:58Z

internal/controller/feature/features.go

 	OtherNames:                                       {Default: false, PreRelease: featuregate.Alpha},
 	UseDomainQualifiedFinalizer:                      {Default: true, PreRelease: featuregate.GA},
-	DefaultPrivateKeyRotationPolicyAlways:            {Default: true, PreRelease: featuregate.Beta},
+	DefaultPrivateKeyRotationPolicyAlways:            {Default: true, PreRelease: featuregate.GA},


This causes the feature flag to become a no-op and hides it from the --help output:

$ make go-workspace $ go run ./cmd/controller/ --help ... --feature-gates mapStringBool A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: ACMEHTTP01IngressPathTypeExact=true|false (BETA - default=true) AllAlpha=true|false (ALPHA - default=false) AllBeta=true|false (BETA - default=false) ExperimentalCertificateSigningRequestControllers=true|false (ALPHA - default=false) ExperimentalGatewayAPISupport=true|false (BETA - default=true) LiteralCertificateSubject=true|false (BETA - default=true) NameConstraints=true|false (BETA - default=true) OtherNames=true|false (ALPHA - default=false) SecretsFilteredCaching=true|false (BETA - default=true) ServerSideApply=true|false (ALPHA - default=false) StableCertificateRequestName=true|false (BETA - default=true) UseCertificateRequestBasicConstraints=true|false (ALPHA - default=false) ValidateCAA=true|false (ALPHA - default=false)

$ go run ./cmd/controller/ --feature-gates DefaultPrivateKeyRotationPolicyAlways=true W1202 16:26:13.124567 59192 feature_gate.go:352] Setting GA feature gate DefaultPrivateKeyRotationPolicyAlways=true. It will be removed in a future release. I1202 16:26:13.124685 59192 controller.go:74] "starting cert-manager controller" logger="cert-manager.controller" version="canary" git_commit="" go_version="go1.25.4" platform="linux/amd64"

inteon · 2025-12-02T18:23:28Z

/approve
/lgtm

cert-manager-prow · 2025-12-02T18:23:36Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: inteon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [inteon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

…#4581) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [cert-manager/cert-manager](https://github.com/cert-manager/cert-manager) | minor | `v1.19.4` → `v1.20.0` | --- ### Release Notes <details> <summary>cert-manager/cert-manager (cert-manager/cert-manager)</summary> ### [`v1.20.0`](https://github.com/cert-manager/cert-manager/releases/tag/v1.20.0) [Compare Source](cert-manager/cert-manager@v1.19.4...v1.20.0) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.20.0 adds support for the new ListenerSet resource, adds support for Azure Private DNS; parentRefs are no longer required when using ACME with Gateway API, and OtherNames was promoted to Beta. #### Changes by Kind ##### Feature - Added a set of flags to permit setting NetworkPolicy across all deployed containers. Remove redundant global IP ranges from example policies. ([#8370](cert-manager/cert-manager#8370), [@jcpunk](https://github.com/jcpunk)) - Added selectable fields to custom resource definitions for .spec.issuerRef.{group, kind, name} ([#8256](cert-manager/cert-manager#8256), [@tareksha](https://github.com/tareksha)) - Added support for specifying `imagePullSecrets` in the `startupapicheck-job` Helm template to enable pulling images from private registries. ([#8186](cert-manager/cert-manager#8186), [@mathieu-clnk](https://github.com/mathieu-clnk)) - Added 'extraContainers' helm chart value, allowing the deployment of arbitrary sidecar containers within the cert-manager operator pod. This can be used to support, for e.g., AWS IAM Roles Anywhere for Route53 DNS01 verification. ([#8355](cert-manager/cert-manager#8355), [@dancmeyers](https://github.com/dancmeyers)) - Added `parentRef` override annotations on the Certificate resource. ([#8518](cert-manager/cert-manager#8518), [@hjoshi123](https://github.com/hjoshi123)) - Added support for azure private zones for dns01 issuer. ([#8494](cert-manager/cert-manager#8494), [@hjoshi123](https://github.com/hjoshi123)) - Added support for configuring PEM decoding size limits, allowing operators to handle larger certificates and keys. ([#7642](cert-manager/cert-manager#7642), [@robertlestak](https://github.com/robertlestak)) - Added support for unhealthyPodEvictionPolicy in PodDisruptionBudget ([#7728](cert-manager/cert-manager#7728), [@jcpunk](https://github.com/jcpunk)) - For Venafi provider, read `venafi.cert-manager.io/custom-fields` annotation on Issuer/ClusterIssuer and use it as base with override/append capabilities on Certificate level. ([#8301](cert-manager/cert-manager#8301), [@k0da](https://github.com/k0da)) - Improve error message when CA issuers are misconfigured to use a clashing secret name ([#8374](cert-manager/cert-manager#8374), [@majiayu000](https://github.com/majiayu000)) - Introduce a new Ingress annotation `acme.cert-manager.io/http01-ingress-ingressclassname` to override `http01.ingress.ingressClassName` field in HTTP-01 challenge solvers. ([#8244](cert-manager/cert-manager#8244), [@lunarwhite](https://github.com/lunarwhite)) - Update `global.nodeSelector` to helm chart to perform a `merge` and allow for a single `nodeSelector` to be set across all services. ([#8195](cert-manager/cert-manager#8195), [@StingRayZA](https://github.com/StingRayZA)) - Vault issuers will now include the Vault server address as one of the default audiences on generated service account tokens. ([#8228](cert-manager/cert-manager#8228), [@terinjokes](https://github.com/terinjokes)) - Added experimental `XListenerSet` feature gate ([#8394](cert-manager/cert-manager#8394), [@hjoshi123](https://github.com/hjoshi123)) ##### Documentation - Add GWAPI documentation to NOTES.TXT in helm chart ([#8353](cert-manager/cert-manager#8353), [@jaxels10](https://github.com/jaxels10)) ##### Bug or Regression - Adds logs for cases when acme server returns us a fatal error in the order controller ([#8199](cert-manager/cert-manager#8199), [@Peac36](https://github.com/Peac36)) - Fixed an issue where kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed ([#8160](cert-manager/cert-manager#8160), [@inteon](https://github.com/inteon)) - Changes to the Duration and RenewBefore annotations on ingress and gateway-api resources will now trigger certificate updates. ([#8232](cert-manager/cert-manager#8232), [@eleanor-merry](https://github.com/eleanor-merry)) - Fix an issue where ACME challenge TXT records are not cleaned up when there are many resource records in CloudDNS. ([#8456](cert-manager/cert-manager#8456), [@tkna](https://github.com/tkna)) - Fix unregulated retries with the DigitalOcean DNS-01 solver Add full detailed DNS-01 errors to the events attached to the Challenge, for easier debugging ([#8221](cert-manager/cert-manager#8221), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. ([#8403](cert-manager/cert-manager#8403), [@calm329](https://github.com/calm329)) - Fixed an issue where HTTP-01 challenges failed when the Host header contains an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. ([#8424](cert-manager/cert-manager#8424), [@SlashNephy](https://github.com/SlashNephy)) - Fixed the HTTP-01 Gateway solver creating invalid HTTPRoutes by not setting spec.hostnames when the challenge DNSName is an IP address. ([#8443](cert-manager/cert-manager#8443), [@alviss7](https://github.com/alviss7)) - Revert API defaults for issuer reference kind and group introduced in 0.19.0 ([#8173](cert-manager/cert-manager#8173), [@erikgb](https://github.com/erikgb)) - Security (MODERATE): Fix a potential panic in the cert-manager controller when a DNS response in an unexpected order was cached. If an attacker was able to modify DNS responses (or if they controlled the DNS server) it was possible to cause denial of service for the cert-manager controller. ([#8469](cert-manager/cert-manager#8469), [@SgtCoDFish](https://github.com/SgtCoDFish)) - Update Go to `v1.25.5` to fix `CVE-2025-61727` and `CVE-2025-61729` ([#8290](cert-manager/cert-manager#8290), [@octo-sts](https://github.com/octo-sts)\[bot]) - When Prometheus monitoring is enabled, the metrics label is now set to the intended value of `cert-manager`. Previously, it was set depending on various factors (namespace cert-manager is installed in and/or Helm release name). ([#8162](cert-manager/cert-manager#8162), [@LiquidPL](https://github.com/LiquidPL)) ##### Other (Cleanup or Flake) - Promoted the OtherNames feature to Beta and enabled it by default ([#8288](cert-manager/cert-manager#8288), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Promoting `xlistenerset` feature gate to `listenerset` ([#8501](cert-manager/cert-manager#8501), [@hjoshi123](https://github.com/hjoshi123)) - Rebranding of the Venafi Issuer to CyberArk ([#8215](cert-manager/cert-manager#8215), [@iossifbenbassat123](https://github.com/iossifbenbassat123)) - Switched to SSA for challenge finalizer updates ([#8519](cert-manager/cert-manager#8519), [@inteon](https://github.com/inteon)) - The default container user (UID) is now 65532 (previously 1000) and the default container group (GID) is now 65532 (previously 0) ([#8408](cert-manager/cert-manager#8408), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - The feature-gate DefaultPrivateKeyRotationPolicyAlways moved from Beta to GA and can no longer be disabled. ([#8287](cert-manager/cert-manager#8287), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Update cert-manager's ACME client, forked from golang/x/crypto ([#8268](cert-manager/cert-manager#8268), [@SgtCoDFish](https://github.com/SgtCoDFish)) - Use the latest version of Kyverno (1.16.2) in the best-practice installation tests ([#8389](cert-manager/cert-manager#8389), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - We stopped testing with Coutour due to it not supporting the new XListenerSet resource, and moved to kgateway. ([#8426](cert-manager/cert-manager#8426), [@hjoshi123](https://github.com/hjoshi123)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://gitea.alexlebens.dev/alexlebens/infrastructure/pulls/4581 Co-authored-by: Renovate Bot <renovate-bot@alexlebens.net> Co-committed-by: Renovate Bot <renovate-bot@alexlebens.net>

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [cert-manager](https://cert-manager.io) ([source](https://github.com/cert-manager/cert-manager)) | minor | `v1.19.4` → `v1.20.0` | --- ### Release Notes <details> <summary>cert-manager/cert-manager (cert-manager)</summary> ### [`v1.20.0`](https://github.com/cert-manager/cert-manager/releases/tag/v1.20.0) [Compare Source](cert-manager/cert-manager@v1.19.4...v1.20.0) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.20.0 adds support for the new ListenerSet resource, adds support for Azure Private DNS; parentRefs are no longer required when using ACME with Gateway API, and OtherNames was promoted to Beta. #### Changes by Kind ##### Feature - Added a set of flags to permit setting NetworkPolicy across all deployed containers. Remove redundant global IP ranges from example policies. ([#8370](cert-manager/cert-manager#8370), [@jcpunk](https://github.com/jcpunk)) - Added selectable fields to custom resource definitions for .spec.issuerRef.{group, kind, name} ([#8256](cert-manager/cert-manager#8256), [@tareksha](https://github.com/tareksha)) - Added support for specifying `imagePullSecrets` in the `startupapicheck-job` Helm template to enable pulling images from private registries. ([#8186](cert-manager/cert-manager#8186), [@mathieu-clnk](https://github.com/mathieu-clnk)) - Added 'extraContainers' helm chart value, allowing the deployment of arbitrary sidecar containers within the cert-manager operator pod. This can be used to support, for e.g., AWS IAM Roles Anywhere for Route53 DNS01 verification. ([#8355](cert-manager/cert-manager#8355), [@dancmeyers](https://github.com/dancmeyers)) - Added `parentRef` override annotations on the Certificate resource. ([#8518](cert-manager/cert-manager#8518), [@hjoshi123](https://github.com/hjoshi123)) - Added support for azure private zones for dns01 issuer. ([#8494](cert-manager/cert-manager#8494), [@hjoshi123](https://github.com/hjoshi123)) - Added support for configuring PEM decoding size limits, allowing operators to handle larger certificates and keys. ([#7642](cert-manager/cert-manager#7642), [@robertlestak](https://github.com/robertlestak)) - Added support for unhealthyPodEvictionPolicy in PodDisruptionBudget ([#7728](cert-manager/cert-manager#7728), [@jcpunk](https://github.com/jcpunk)) - For Venafi provider, read `venafi.cert-manager.io/custom-fields` annotation on Issuer/ClusterIssuer and use it as base with override/append capabilities on Certificate level. ([#8301](cert-manager/cert-manager#8301), [@k0da](https://github.com/k0da)) - Improve error message when CA issuers are misconfigured to use a clashing secret name ([#8374](cert-manager/cert-manager#8374), [@majiayu000](https://github.com/majiayu000)) - Introduce a new Ingress annotation `acme.cert-manager.io/http01-ingress-ingressclassname` to override `http01.ingress.ingressClassName` field in HTTP-01 challenge solvers. ([#8244](cert-manager/cert-manager#8244), [@lunarwhite](https://github.com/lunarwhite)) - Update `global.nodeSelector` to helm chart to perform a `merge` and allow for a single `nodeSelector` to be set across all services. ([#8195](cert-manager/cert-manager#8195), [@StingRayZA](https://github.com/StingRayZA)) - Vault issuers will now include the Vault server address as one of the default audiences on generated service account tokens. ([#8228](cert-manager/cert-manager#8228), [@terinjokes](https://github.com/terinjokes)) - Added experimental `XListenerSet` feature gate ([#8394](cert-manager/cert-manager#8394), [@hjoshi123](https://github.com/hjoshi123)) ##### Documentation - Add GWAPI documentation to NOTES.TXT in helm chart ([#8353](cert-manager/cert-manager#8353), [@jaxels10](https://github.com/jaxels10)) ##### Bug or Regression - Adds logs for cases when acme server returns us a fatal error in the order controller ([#8199](cert-manager/cert-manager#8199), [@Peac36](https://github.com/Peac36)) - Fixed an issue where kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed ([#8160](cert-manager/cert-manager#8160), [@inteon](https://github.com/inteon)) - Changes to the Duration and RenewBefore annotations on ingress and gateway-api resources will now trigger certificate updates. ([#8232](cert-manager/cert-manager#8232), [@eleanor-merry](https://github.com/eleanor-merry)) - Fix an issue where ACME challenge TXT records are not cleaned up when there are many resource records in CloudDNS. ([#8456](cert-manager/cert-manager#8456), [@tkna](https://github.com/tkna)) - Fix unregulated retries with the DigitalOcean DNS-01 solver Add full detailed DNS-01 errors to the events attached to the Challenge, for easier debugging ([#8221](cert-manager/cert-manager#8221), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. ([#8403](cert-manager/cert-manager#8403), [@calm329](https://github.com/calm329)) - Fixed an issue where HTTP-01 challenges failed when the Host header contains an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. ([#8424](cert-manager/cert-manager#8424), [@SlashNephy](https://github.com/SlashNephy)) - Fixed the HTTP-01 Gateway solver creating invalid HTTPRoutes by not setting spec.hostnames when the challenge DNSName is an IP address. ([#8443](cert-manager/cert-manager#8443), [@alviss7](https://github.com/alviss7)) - Revert API defaults for issuer reference kind and group introduced in 0.19.0 ([#8173](cert-manager/cert-manager#8173), [@erikgb](https://github.com/erikgb)) - Security (MODERATE): Fix a potential panic in the cert-manager controller when a DNS response in an unexpected order was cached. If an attacker was able to modify DNS responses (or if they controlled the DNS server) it was possible to cause denial of service for the cert-manager controller. ([#8469](cert-manager/cert-manager#8469), [@SgtCoDFish](https://github.com/SgtCoDFish)) - Update Go to `v1.25.5` to fix `CVE-2025-61727` and `CVE-2025-61729` ([#8290](cert-manager/cert-manager#8290), [@octo-sts](https://github.com/octo-sts)\[bot]) - When Prometheus monitoring is enabled, the metrics label is now set to the intended value of `cert-manager`. Previously, it was set depending on various factors (namespace cert-manager is installed in and/or Helm release name). ([#8162](cert-manager/cert-manager#8162), [@LiquidPL](https://github.com/LiquidPL)) ##### Other (Cleanup or Flake) - Promoted the OtherNames feature to Beta and enabled it by default ([#8288](cert-manager/cert-manager#8288), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Promoting `xlistenerset` feature gate to `listenerset` ([#8501](cert-manager/cert-manager#8501), [@hjoshi123](https://github.com/hjoshi123)) - Rebranding of the Venafi Issuer to CyberArk ([#8215](cert-manager/cert-manager#8215), [@iossifbenbassat123](https://github.com/iossifbenbassat123)) - Switched to SSA for challenge finalizer updates ([#8519](cert-manager/cert-manager#8519), [@inteon](https://github.com/inteon)) - The default container user (UID) is now 65532 (previously 1000) and the default container group (GID) is now 65532 (previously 0) ([#8408](cert-manager/cert-manager#8408), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - The feature-gate DefaultPrivateKeyRotationPolicyAlways moved from Beta to GA and can no longer be disabled. ([#8287](cert-manager/cert-manager#8287), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - Update cert-manager's ACME client, forked from golang/x/crypto ([#8268](cert-manager/cert-manager#8268), [@SgtCoDFish](https://github.com/SgtCoDFish)) - Use the latest version of Kyverno (1.16.2) in the best-practice installation tests ([#8389](cert-manager/cert-manager#8389), [@wallrj-cyberark](https://github.com/wallrj-cyberark)) - We stopped testing with Coutour due to it not supporting the new XListenerSet resource, and moved to kgateway. ([#8426](cert-manager/cert-manager#8426), [@hjoshi123](https://github.com/hjoshi123)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://gitea.alexlebens.dev/alexlebens/infrastructure/pulls/4582 Co-authored-by: Renovate Bot <renovate-bot@alexlebens.net> Co-committed-by: Renovate Bot <renovate-bot@alexlebens.net>

wallrj-cyberark added the cybr Used by CyberArk-employed maintainers to report to line management what's being worked on. label Dec 2, 2025

wallrj-cyberark self-assigned this Dec 2, 2025

wallrj-cyberark force-pushed the remove-private-key-rotation-warning branch from bd8a9da to 71014c3 Compare December 2, 2025 16:34

wallrj-cyberark commented Dec 2, 2025

View reviewed changes

wallrj-cyberark changed the title ~~WIP: Graduate DefaultPrivateKeyRotationPolicyAlways to GA and remove gating~~ Graduate DefaultPrivateKeyRotationPolicyAlways to GA and remove gating Dec 2, 2025

cert-manager-prow bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 2, 2025

wallrj-cyberark requested a review from inteon December 2, 2025 17:10

wallrj-cyberark mentioned this pull request Dec 2, 2025

Promote OtherNames to Beta and enable by default #8288

Merged

cert-manager-prow bot added the lgtm Indicates that a PR is ready to be merged. label Dec 2, 2025

cert-manager-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 2, 2025

cert-manager-prow bot merged commit 44f5769 into cert-manager:master Dec 2, 2025
6 checks passed

wallrj-cyberark deleted the remove-private-key-rotation-warning branch December 3, 2025 09:25

github-actions bot mentioned this pull request Mar 30, 2026

Update Helm release cert-manager to v1.20.0 claytono/infra#1873

Merged

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Graduate DefaultPrivateKeyRotationPolicyAlways to GA and remove gating#8287

Graduate DefaultPrivateKeyRotationPolicyAlways to GA and remove gating#8287
cert-manager-prow[bot] merged 1 commit intocert-manager:masterfrom
wallrj-cyberark:remove-private-key-rotation-warning

wallrj-cyberark commented Dec 2, 2025 •

edited

Loading

Uh oh!

wallrj-cyberark Dec 2, 2025

Uh oh!

wallrj-cyberark Dec 2, 2025

Uh oh!

wallrj-cyberark Dec 2, 2025

Uh oh!

wallrj-cyberark Dec 2, 2025

Uh oh!

wallrj-cyberark Dec 2, 2025

Uh oh!

wallrj-cyberark Dec 2, 2025

Uh oh!

wallrj-cyberark Dec 2, 2025

Uh oh!

wallrj-cyberark Dec 2, 2025

Uh oh!

wallrj-cyberark Dec 2, 2025

Uh oh!

inteon commented Dec 2, 2025

Uh oh!

cert-manager-prow bot commented Dec 2, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

wallrj-cyberark commented Dec 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Testing

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

inteon commented Dec 2, 2025

Uh oh!

cert-manager-prow bot commented Dec 2, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

wallrj-cyberark commented Dec 2, 2025 •

edited

Loading