feat(container): update image quay.io/jetstack/charts/cert-manager ( v1.18.2 → v1.19.4 ) by renovate[bot] · Pull Request #518 · roblandry/home-ops

renovate · 2025-10-11T16:41:36Z

This PR contains the following updates:

Package	Update	Change
quay.io/jetstack/charts/cert-manager (source)	minor	`v1.18.2` → `v1.19.4`

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

cert-manager/cert-manager (quay.io/jetstack/charts/cert-manager)

`v1.19.4`

Compare Source

`v1.19.4`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

v1.19.4 is a simple patch release to fix some reported vulnerabilities - notably CVE-2026-24051 and CVE-2025-68121. All users should upgrade.

Changes by Kind

Bug or Regression

Bump go to address CVE-2025-68121 (#8526, @SgtCoDFish)
Bump otel SDK to address GO-2026-4394 (#8531, @SgtCoDFish)

`v1.19.3`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This release contains three bug fixes, including a fix for the MODERATE severity DoS issue in GHSA-gx3x-vq4p-mhhv. All users should upgrade to the latest release.

Changes by Kind

Bug or Regression

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. (#8415, @cert-manager-bot)
Fixed an issue where HTTP-01 challenges failed when the Host header contained an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. (#8436, @cert-manager-bot)
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. (#8468, @SgtCoDFish)

Other (Cleanup or Flake)

Bump go to 1.25.6 (#8459, @SgtCoDFish)

`v1.19.3`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This release contains three bug fixes, including a fix for the MODERATE severity DoS issue in GHSA-gx3x-vq4p-mhhv. All users should upgrade to the latest release.

Changes by Kind

Bug or Regression

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. (#8415, @cert-manager-bot)
Fixed an issue where HTTP-01 challenges failed when the Host header contained an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. (#8436, @cert-manager-bot)
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. (#8468, @SgtCoDFish)

Other (Cleanup or Flake)

Bump go to 1.25.6 (#8459, @SgtCoDFish)

`v1.19.2`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We updated Go to fix some vulnerabilities in the standard library.

📖 Read the full 1.19 release notes on the cert-manager.io website before upgrading.

Changes since `v1.19.1`

Bug or Regression

Address false positive vulnerabilities CVE-2025-47914 and CVE-2025-58181 which were reported by Trivy. (#8283, @SgtCoDFish)
Update Go to v1.25.5 to fix CVE-2025-61727 and CVE-2025-61729 (#8294, @wallrj-cyberark)
Update global.nodeSelector to helm chart to perform a merge and allow for a single nodeSelector to be set across all services. (#8233, @cert-manager-bot)

Other (Cleanup or Flake)

Update cert-manager's ACME client, forked from golang/x/crypto (#8270, @SgtCoDFish)
Updated Debian 12 distroless base images (#8326, @wallrj-cyberark)

`v1.19.2`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We updated Go to fix some vulnerabilities in the standard library.

📖 Read the full 1.19 release notes on the cert-manager.io website before upgrading.

Changes since `v1.19.1`

Bug or Regression

Address false positive vulnerabilities CVE-2025-47914 and CVE-2025-58181 which were reported by Trivy. (#8283, @SgtCoDFish)
Update Go to v1.25.5 to fix CVE-2025-61727 and CVE-2025-61729 (#8294, @wallrj-cyberark)
Update global.nodeSelector to helm chart to perform a merge and allow for a single nodeSelector to be set across all services. (#8233, @cert-manager-bot)

Other (Cleanup or Flake)

Update cert-manager's ACME client, forked from golang/x/crypto (#8270, @SgtCoDFish)
Updated Debian 12 distroless base images (#8326, @wallrj-cyberark)

`v1.19.1`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We reverted the CRD-based API defaults for Certificate.Spec.IssuerRef and CertificateRequest.Spec.IssuerRef after they were found to cause unexpected certificate renewals after upgrading to 1.19.0. We will try re-introducing these API defaults in cert-manager 1.20.
We fixed a bug that caused certificates to be re-issued unexpectedly if the issuerRef kind or group was changed to one of the "runtime" default values.
We upgraded Go to 1.25.3 to address the following security vulnerabilities: CVE-2025-61724, CVE-2025-58187, CVE-2025-47912, CVE-2025-58183, CVE-2025-61723, CVE-2025-58186, CVE-2025-58185, CVE-2025-58188, and CVE-2025-61725.

📖 Read the full 1.19 release notes on the cert-manager.io website before upgrading.

Changes since v1.19.0:

Bug or Regression

BUGFIX: in case kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed (#8175, @cert-manager-bot)
Bump Go to 1.25.3 to fix a backwards incompatible change to the validation of DNS names in X.509 SAN fields which prevented the use of DNS names with a trailing dot (#8177, @wallrj-cyberark)
Revert API defaults for issuer reference kind and group introduced in 0.19.0 (#8178, @cert-manager-bot)

`v1.19.1`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We reverted the CRD-based API defaults for Certificate.Spec.IssuerRef and CertificateRequest.Spec.IssuerRef after they were found to cause unexpected certificate renewals after upgrading to 1.19.0. We will try re-introducing these API defaults in cert-manager 1.20.
We fixed a bug that caused certificates to be re-issued unexpectedly if the issuerRef kind or group was changed to one of the "runtime" default values.
We upgraded Go to 1.25.3 to address the following security vulnerabilities: CVE-2025-61724, CVE-2025-58187, CVE-2025-47912, CVE-2025-58183, CVE-2025-61723, CVE-2025-58186, CVE-2025-58185, CVE-2025-58188, and CVE-2025-61725.

📖 Read the full 1.19 release notes on the cert-manager.io website before upgrading.

Changes since v1.19.0:

Bug or Regression

BUGFIX: in case kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed (#8175, @cert-manager-bot)
Bump Go to 1.25.3 to fix a backwards incompatible change to the validation of DNS names in X.509 SAN fields which prevented the use of DNS names with a trailing dot (#8177, @wallrj-cyberark)
Revert API defaults for issuer reference kind and group introduced in 0.19.0 (#8178, @cert-manager-bot)

`v1.19.0`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

⚠️ Known issues: The following known issues are fixed in v1.19.1:

Unexpected certificate renewal after upgrading to 1.19.0

This release focuses on expanding platform compatibility, improving deployment flexibility, enhancing observability, and addressing key reliability issues.

📖 Read the full release notes at cert-manager.io: https://cert-manager.io/docs/releases/release-notes/release-notes-1.19

Changes since v1.18.0:

Feature

Add IPv6 rules to the default network policy (#7726, @jcpunk)
Add global.nodeSelector to helm chart to allow for a single nodeSelector to be set across all services. (#7818, @StingRayZA)
Add a feature gate to default to Ingress pathType Exact in ACME HTTP01 Ingress challenge solvers. (#7795, @sspreitzer)
Add generated applyconfigurations allowing clients to make type-safe server-side apply requests for cert-manager resources. (#7866, @erikgb)
Added API defaults to issuer references group (cert-manager.io) and kind (Issuer). (#7414, @erikgb)
Added certmanager_certificate_challenge_status Prometheus metric. (#7736, @hjoshi123)
Added protocol field for rfc2136 DNS01 provider (#7881, @hjoshi123)
Added experimental field hostUsers flag to all pods. Not set by default. (#7973, @hjoshi123)
Support configurable resource requests and limits for ACME HTTP01 solver pods through ClusterIssuer and Issuer specifications, allowing granular resource management that overrides global --acme-http01-solver-resource-* settings. (#7972, @lunarwhite)
The CAInjectorMerging feature has been promoted to BETA and is now enabled by default (#8017, @ThatsMrTalbot)
The controller, webhook and ca-injector now log their version and git commit on startup for easier debugging and support. (#8072, @prasad89)
Updated certificate metrics to the collector approach. (#7856, @hjoshi123)

Bug or Regression

ACME: Increased challenge authorization timeout to 2 minutes to fix error waiting for authorization (#7796, @hjoshi123)
BUGFIX: permitted URI domains were incorrectly used to set the excluded URI domains in the CSR's name constraints (#7816, @kinolaev)
Enforced ACME HTTP-01 solver validation to properly reject configurations when multiple ingress options (class, ingressClassName, name) are specified simultaneously (#8021, @lunarwhite)
Increase maximum sizes of PEM certificates and chains which can be parsed in cert-manager, to handle leaf certificates with large numbers of DNS names or other identities (#7961, @SgtCoDFish)
Reverted adding the global.rbac.disableHTTPChallengesRole Helm option. (#7836, @inteon)
This change removes the path label of core ACME client metrics and will require users to update their monitoring dashboards and alerting rules if using those metrics. (#8109, @mladen-rusev-cyberark)
Use the latest version of ingress-nginx in E2E tests to ensure compatibility (#7792, @wallrj)

Other (Cleanup or Flake)

Helm: Fix naming template of tokenrequest RoleBinding resource to improve consistency (#7761, @lunarwhite)
Improve error messages when certificates, CRLs or private keys fail admission due to malformed or missing PEM data (#7928, @SgtCoDFish)
Major upgrade of Akamai SDK. NOTE: The new version has not been fully tested end-to-end due to the lack of cloud infrastructure. (#8003, @hjoshi123)
Update kind images to include the Kubernetes 1.33 node image (#7786, @wallrj)
Use maps.Copy for cleaner map handling (#8092, @quantpoet)
Vault: Migrate Vault E2E add-on tests from deprecated vault-client-go to the new vault/api client. (#8059, @armagankaratosun)

`v1.19.0`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

⚠️ Known issues: The following known issues are fixed in v1.19.1:

Unexpected certificate renewal after upgrading to 1.19.0

This release focuses on expanding platform compatibility, improving deployment flexibility, enhancing observability, and addressing key reliability issues.

📖 Read the full release notes at cert-manager.io: https://cert-manager.io/docs/releases/release-notes/release-notes-1.19

Changes since v1.18.0:

Feature

Add IPv6 rules to the default network policy (#7726, @jcpunk)
Add global.nodeSelector to helm chart to allow for a single nodeSelector to be set across all services. (#7818, @StingRayZA)
Add a feature gate to default to Ingress pathType Exact in ACME HTTP01 Ingress challenge solvers. (#7795, @sspreitzer)
Add generated applyconfigurations allowing clients to make type-safe server-side apply requests for cert-manager resources. (#7866, @erikgb)
Added API defaults to issuer references group (cert-manager.io) and kind (Issuer). (#7414, @erikgb)
Added certmanager_certificate_challenge_status Prometheus metric. (#7736, @hjoshi123)
Added protocol field for rfc2136 DNS01 provider (#7881, @hjoshi123)
Added experimental field hostUsers flag to all pods. Not set by default. (#7973, @hjoshi123)
Support configurable resource requests and limits for ACME HTTP01 solver pods through ClusterIssuer and Issuer specifications, allowing granular resource management that overrides global --acme-http01-solver-resource-* settings. (#7972, @lunarwhite)
The CAInjectorMerging feature has been promoted to BETA and is now enabled by default (#8017, @ThatsMrTalbot)
The controller, webhook and ca-injector now log their version and git commit on startup for easier debugging and support. (#8072, @prasad89)
Updated certificate metrics to the collector approach. (#7856, @hjoshi123)

Bug or Regression

ACME: Increased challenge authorization timeout to 2 minutes to fix error waiting for authorization (#7796, @hjoshi123)
BUGFIX: permitted URI domains were incorrectly used to set the excluded URI domains in the CSR's name constraints (#7816, @kinolaev)
Enforced ACME HTTP-01 solver validation to properly reject configurations when multiple ingress options (class, ingressClassName, name) are specified simultaneously (#8021, @lunarwhite)
Increase maximum sizes of PEM certificates and chains which can be parsed in cert-manager, to handle leaf certificates with large numbers of DNS names or other identities (#7961, @SgtCoDFish)
Reverted adding the global.rbac.disableHTTPChallengesRole Helm option. (#7836, @inteon)
This change removes the path label of core ACME client metrics and will require users to update their monitoring dashboards and alerting rules if using those metrics. (#8109, @mladen-rusev-cyberark)
Use the latest version of ingress-nginx in E2E tests to ensure compatibility (#7792, @wallrj)

Other (Cleanup or Flake)

Helm: Fix naming template of tokenrequest RoleBinding resource to improve consistency (#7761, @lunarwhite)
Improve error messages when certificates, CRLs or private keys fail admission due to malformed or missing PEM data (#7928, @SgtCoDFish)
Major upgrade of Akamai SDK. NOTE: The new version has not been fully tested end-to-end due to the lack of cloud infrastructure. (#8003, @hjoshi123)
Update kind images to include the Kubernetes 1.33 node image (#7786, @wallrj)
Use maps.Copy for cleaner map handling (#8092, @quantpoet)
Vault: Migrate Vault E2E add-on tests from deprecated vault-client-go to the new vault/api client. (#8059, @armagankaratosun)

`v1.18.5`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This release contains three bug fixes, including a fix for the MODERATE severity DoS issue in GHSA-gx3x-vq4p-mhhv. All users should upgrade to the latest release.

Changes by Kind

Bug or Regression

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. (#8414, @cert-manager-bot)
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. (#8437, @cert-manager-bot)
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. (#8467, @SgtCoDFish)

Other (Cleanup or Flake)

Bump go to 1.24.12 (#8460, @SgtCoDFish)

`v1.18.5`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This release contains three bug fixes, including a fix for the MODERATE severity DoS issue in GHSA-gx3x-vq4p-mhhv. All users should upgrade to the latest release.

Changes by Kind

Bug or Regression

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. (#8414, @cert-manager-bot)
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. (#8437, @cert-manager-bot)
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. (#8467, @SgtCoDFish)

Other (Cleanup or Flake)

Bump go to 1.24.12 (#8460, @SgtCoDFish)

`v1.18.4`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We updated Go to fix some vulnerabilities in the standard library.

📖 Read the full 1.18 release notes on the cert-manager.io website before upgrading.

Changes since `v1.18.3`

Bug or Regression

Address false positive vulnerabilities CVE-2025-47914 and CVE-2025-58181 which were reported by Trivy. (#8282, @SgtCoDFish)
Update Go to v1.24.11 to fix CVE-2025-61727 and CVE-2025-61729 (#8295, @wallrj-cyberark)

Other (Cleanup or Flake)

Update cert-manager's ACME client, forked from golang/x/crypto (#8271, @SgtCoDFish)
Updated Debian 12 distroless base images (#8328, @wallrj-cyberark)

`v1.18.4`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We updated Go to fix some vulnerabilities in the standard library.

📖 Read the full 1.18 release notes on the cert-manager.io website before upgrading.

Changes since `v1.18.3`

Bug or Regression

Address false positive vulnerabilities CVE-2025-47914 and CVE-2025-58181 which were reported by Trivy. (#8282, @SgtCoDFish)
Update Go to v1.24.11 to fix CVE-2025-61727 and CVE-2025-61729 (#8295, @wallrj-cyberark)

Other (Cleanup or Flake)

Update cert-manager's ACME client, forked from golang/x/crypto (#8271, @SgtCoDFish)
Updated Debian 12 distroless base images (#8328, @wallrj-cyberark)

`v1.18.3`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We fixed a bug which caused certificates to be re-issued unexpectedly, if the issuerRef kind or group was changed to one of the "runtime" default values. We increased the size limit when parsing PEM certificate chains to handle leaf certificates with large numbers of DNS named or other identities. We upgraded Go to 1.24.9 to fix various non-critical security vulnerabilities.

📖 Read the full 1.18 release notes on the cert-manager.io website before upgrading.

Changes since v1.18.2:

Bug or Regression

BUGFIX: in case kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed (#8174, @cert-manager-bot)
Bump Go to 1.24.9. Fixes the following vulnerabilities: CVE-2025-61724, CVE-2025-58187, CVE-2025-47912, CVE-2025-58183, CVE-2025-61723, CVE-2025-58186, CVE-2025-58185, CVE-2025-58188, CVE-2025-61725 (#8176, @wallrj-cyberark)
Increase maximum sizes of PEM certificates and chains which can be parsed in cert-manager, to handle leaf certificates with large numbers of DNS names or other identities (#7966, @cert-manager-bot)

Other (Cleanup or Flake)

Improve error messages when certificates, CRLs or private keys fail admission due to malformed or missing PEM data (#7964, @cert-manager-bot)
Upgrades Go to v1.24.6 (#7974, @SgtCoDFish)

`v1.18.3`

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

We fixed a bug which caused certificates to be re-issued unexpectedly, if the issuerRef kind or group was changed to one of the "runtime" default values. We increased the size limit when parsing PEM certificate chains to handle leaf certificates with large numbers of DNS named or other identities. We upgraded Go to 1.24.9 to fix various non-critical security vulnerabilities.

📖 Read the full 1.18 release notes on the cert-manager.io website before upgrading.

Changes since v1.18.2:

Bug or Regression

BUGFIX: in case kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed (#8174, @cert-manager-bot)
Bump Go to 1.24.9. Fixes the following vulnerabilities: CVE-2025-61724, CVE-2025-58187, CVE-2025-47912, CVE-2025-58183, CVE-2025-61723, CVE-2025-58186, CVE-2025-58185, CVE-2025-58188, CVE-2025-61725 (#8176, @wallrj-cyberark)
Increase maximum sizes of PEM certificates and chains which can be parsed in cert-manager, to handle leaf certificates with large numbers of DNS names or other identities (#7966, @cert-manager-bot)

Other (Cleanup or Flake)

Improve error messages when certificates, CRLs or private keys fail admission due to malformed or missing PEM data (#7964, @cert-manager-bot)
Upgrades Go to v1.24.6 (#7974, @SgtCoDFish)

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

github-actions · 2025-10-11T16:42:15Z

--- kubernetes/apps/cert-manager/cert-manager/app Kustomization: cert-manager/cert-manager OCIRepository: cert-manager/cert-manager

+++ kubernetes/apps/cert-manager/cert-manager/app Kustomization: cert-manager/cert-manager OCIRepository: cert-manager/cert-manager

@@ -11,9 +11,9 @@

 spec:
   interval: 5m
   layerSelector:
     mediaType: application/vnd.cncf.helm.chart.content.v1.tar+gzip
     operation: copy
   ref:
-    tag: v1.18.2
+    tag: v1.19.4
   url: oci://quay.io/jetstack/charts/cert-manager

github-actions · 2025-10-11T16:42:19Z

--- HelmRelease: cert-manager/cert-manager RoleBinding: cert-manager/cert-manager-cert-manager-tokenrequest

+++ HelmRelease: cert-manager/cert-manager RoleBinding: cert-manager/cert-manager-cert-manager-tokenrequest

@@ -1,21 +0,0 @@

----
-apiVersion: rbac.authorization.k8s.io/v1
-kind: RoleBinding
-metadata:
-  name: cert-manager-cert-manager-tokenrequest
-  namespace: cert-manager
-  labels:
-    app: cert-manager
-    app.kubernetes.io/name: cert-manager
-    app.kubernetes.io/instance: cert-manager
-    app.kubernetes.io/component: controller
-    app.kubernetes.io/managed-by: Helm
-roleRef:
-  apiGroup: rbac.authorization.k8s.io
-  kind: Role
-  name: cert-manager-tokenrequest
-subjects:
-- kind: ServiceAccount
-  name: cert-manager
-  namespace: cert-manager
-
--- HelmRelease: cert-manager/cert-manager Deployment: cert-manager/cert-manager-cainjector

+++ HelmRelease: cert-manager/cert-manager Deployment: cert-manager/cert-manager-cainjector

@@ -31,13 +31,13 @@

       securityContext:
         runAsNonRoot: true
         seccompProfile:
           type: RuntimeDefault
       containers:
       - name: cert-manager-cainjector
-        image: quay.io/jetstack/cert-manager-cainjector:v1.18.2
+        image: quay.io/jetstack/cert-manager-cainjector:v1.19.4
         imagePullPolicy: IfNotPresent
         args:
         - --v=2
         - --leader-election-namespace=kube-system
         ports:
         - containerPort: 9402
--- HelmRelease: cert-manager/cert-manager Deployment: cert-manager/cert-manager

+++ HelmRelease: cert-manager/cert-manager Deployment: cert-manager/cert-manager

@@ -31,19 +31,19 @@

       securityContext:
         runAsNonRoot: true
         seccompProfile:
           type: RuntimeDefault
       containers:
       - name: cert-manager-controller
-        image: quay.io/jetstack/cert-manager-controller:v1.18.2
+        image: quay.io/jetstack/cert-manager-controller:v1.19.4
         imagePullPolicy: IfNotPresent
         args:
         - --v=2
         - --cluster-resource-namespace=$(POD_NAMESPACE)
         - --leader-election-namespace=kube-system
-        - --acme-http01-solver-image=quay.io/jetstack/cert-manager-acmesolver:v1.18.2
+        - --acme-http01-solver-image=quay.io/jetstack/cert-manager-acmesolver:v1.19.4
         - --max-concurrent-challenges=60
         - --dns01-recursive-nameservers-only=true
         - --dns01-recursive-nameservers=https://1.1.1.1:443/dns-query,https://1.0.0.1:443/dns-query
         ports:
         - containerPort: 9402
           name: http-metrics
--- HelmRelease: cert-manager/cert-manager Deployment: cert-manager/cert-manager-webhook

+++ HelmRelease: cert-manager/cert-manager Deployment: cert-manager/cert-manager-webhook

@@ -31,13 +31,13 @@

       securityContext:
         runAsNonRoot: true
         seccompProfile:
           type: RuntimeDefault
       containers:
       - name: cert-manager-webhook
-        image: quay.io/jetstack/cert-manager-webhook:v1.18.2
+        image: quay.io/jetstack/cert-manager-webhook:v1.19.4
         imagePullPolicy: IfNotPresent
         args:
         - --v=2
         - --secure-port=10250
         - --dynamic-serving-ca-secret-namespace=$(POD_NAMESPACE)
         - --dynamic-serving-ca-secret-name=cert-manager-webhook-ca
--- HelmRelease: cert-manager/cert-manager Job: cert-manager/cert-manager-startupapicheck

+++ HelmRelease: cert-manager/cert-manager Job: cert-manager/cert-manager-startupapicheck

@@ -31,13 +31,13 @@

       securityContext:
         runAsNonRoot: true
         seccompProfile:
           type: RuntimeDefault
       containers:
       - name: cert-manager-startupapicheck
-        image: quay.io/jetstack/cert-manager-startupapicheck:v1.18.2
+        image: quay.io/jetstack/cert-manager-startupapicheck:v1.19.4
         imagePullPolicy: IfNotPresent
         args:
         - check
         - api
         - --wait=1m
         - -v
--- HelmRelease: cert-manager/cert-manager RoleBinding: cert-manager/cert-manager-tokenrequest

+++ HelmRelease: cert-manager/cert-manager RoleBinding: cert-manager/cert-manager-tokenrequest

@@ -0,0 +1,21 @@

+---
+apiVersion: rbac.authorization.k8s.io/v1
+kind: RoleBinding
+metadata:
+  name: cert-manager-tokenrequest
+  namespace: cert-manager
+  labels:
+    app: cert-manager
+    app.kubernetes.io/name: cert-manager
+    app.kubernetes.io/instance: cert-manager
+    app.kubernetes.io/component: controller
+    app.kubernetes.io/managed-by: Helm
+roleRef:
+  apiGroup: rbac.authorization.k8s.io
+  kind: Role
+  name: cert-manager-tokenrequest
+subjects:
+- kind: ServiceAccount
+  name: cert-manager
+  namespace: cert-manager
+

…v1.18.2 → v1.19.4 )

renovate bot added renovate/container type/minor labels Oct 11, 2025

github-actions bot added area/kubernetes area/bootstrap labels Oct 11, 2025

renovate bot force-pushed the renovate/cert-manager branch from 4205a3c to 5a82e98 Compare October 15, 2025 18:10

renovate bot changed the title ~~feat(container): update image quay.io/jetstack/charts/cert-manager ( v1.18.2 → v1.19.0 )~~ feat(container): update image quay.io/jetstack/charts/cert-manager ( v1.18.2 → v1.19.1 ) Oct 15, 2025

renovate bot force-pushed the renovate/cert-manager branch from 5a82e98 to 1078e16 Compare October 22, 2025 00:06

renovate bot force-pushed the renovate/cert-manager branch from 1078e16 to 755bf1b Compare November 10, 2025 20:10

renovate bot force-pushed the renovate/cert-manager branch from 755bf1b to ff51106 Compare December 3, 2025 18:48

renovate bot changed the title ~~feat(container): update image quay.io/jetstack/charts/cert-manager ( v1.18.2 → v1.19.1 )~~ feat(container): update image quay.io/jetstack/charts/cert-manager ( v1.18.2 → v1.19.2 ) Dec 9, 2025

renovate bot force-pushed the renovate/cert-manager branch from ff51106 to 8520c81 Compare December 9, 2025 16:09

renovate bot force-pushed the renovate/cert-manager branch from 8520c81 to 90620c4 Compare January 8, 2026 18:37

renovate bot force-pushed the renovate/cert-manager branch from 90620c4 to 6361bd5 Compare January 23, 2026 18:11

renovate bot force-pushed the renovate/cert-manager branch from 6361bd5 to 7eaafbc Compare February 2, 2026 21:43

renovate bot changed the title ~~feat(container): update image quay.io/jetstack/charts/cert-manager ( v1.18.2 → v1.19.2 )~~ feat(container): update image quay.io/jetstack/charts/cert-manager ( v1.18.2 → v1.19.3 ) Feb 2, 2026

renovate bot force-pushed the renovate/cert-manager branch from 7eaafbc to c40238a Compare February 12, 2026 16:08

feat(container): update image quay.io/jetstack/charts/cert-manager ( …

2d2bac4

…v1.18.2 → v1.19.4 )

renovate bot force-pushed the renovate/cert-manager branch from c40238a to 2d2bac4 Compare February 24, 2026 19:03

renovate bot changed the title ~~feat(container): update image quay.io/jetstack/charts/cert-manager ( v1.18.2 → v1.19.3 )~~ feat(container): update image quay.io/jetstack/charts/cert-manager ( v1.18.2 → v1.19.4 ) Feb 24, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(container): update image quay.io/jetstack/charts/cert-manager ( v1.18.2 → v1.19.4 )#518

feat(container): update image quay.io/jetstack/charts/cert-manager ( v1.18.2 → v1.19.4 )#518
renovate[bot] wants to merge 1 commit intomainfrom
renovate/cert-manager

renovate bot commented Oct 11, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Oct 11, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Oct 11, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate bot commented Oct 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Changes by Kind

Bug or Regression

Changes by Kind

Bug or Regression

Other (Cleanup or Flake)

Changes by Kind

Bug or Regression

Other (Cleanup or Flake)

Changes since v1.19.1

Bug or Regression

Other (Cleanup or Flake)

Changes since v1.19.1

Bug or Regression

Other (Cleanup or Flake)

Bug or Regression

Bug or Regression

Feature

Bug or Regression

Other (Cleanup or Flake)

Feature

Bug or Regression

Other (Cleanup or Flake)

Changes by Kind

Bug or Regression

Other (Cleanup or Flake)

Changes by Kind

Bug or Regression

Other (Cleanup or Flake)

Changes since v1.18.3

Bug or Regression

Other (Cleanup or Flake)

Changes since v1.18.3

Bug or Regression

Other (Cleanup or Flake)

Bug or Regression

Other (Cleanup or Flake)

Bug or Regression

Other (Cleanup or Flake)

Configuration

Uh oh!

github-actions bot commented Oct 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Oct 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Oct 11, 2025 •

edited

Loading

Changes since `v1.19.1`

Changes since `v1.19.1`

Changes since `v1.18.3`

Changes since `v1.18.3`

github-actions bot commented Oct 11, 2025 •

edited

Loading

github-actions bot commented Oct 11, 2025 •

edited

Loading