Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 9, 2025

This PR contains the following updates:

Package Update Change
cert-manager/cert-manager minor 1.18.2 -> 1.19.1

Warning

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


Release Notes

cert-manager/cert-manager (cert-manager/cert-manager)

v1.19.1

Compare Source

v1.19.0

Compare Source

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

⚠️ Known issues: We are working on a patch to fix the following issues:

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.3

Compare Source


Configuration

📅 Schedule: Branch creation - "before 5am every weekday" (UTC), 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Oct 9, 2025
@renovate renovate bot requested a review from a team as a code owner October 9, 2025 02:11
@renovate renovate bot added the dependencies label Oct 9, 2025
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch 6 times, most recently from a91584a to e683b44 Compare October 10, 2025 13:21
@pmalek pmalek added this pull request to the merge queue Oct 10, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 10, 2025
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch 7 times, most recently from 695fa5e to 91033da Compare October 13, 2025 11:56
@pmalek pmalek added this pull request to the merge queue Oct 14, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 14, 2025
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch from 91033da to 58d4f8b Compare October 14, 2025 10:09
@pmalek pmalek added this pull request to the merge queue Oct 14, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 14, 2025
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch 4 times, most recently from d9a9a35 to d2a5e97 Compare October 14, 2025 14:48
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch 3 times, most recently from 8c8a379 to 3f6b254 Compare October 15, 2025 09:26
pmalek
pmalek previously approved these changes Oct 15, 2025
@pmalek pmalek added this pull request to the merge queue Oct 15, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 15, 2025
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch 5 times, most recently from 14cc7ff to d469548 Compare October 15, 2025 15:27
@renovate renovate bot changed the title chore(deps): update dependency cert-manager/cert-manager to v1.19.0 chore(deps): update dependency cert-manager/cert-manager to v1.19.1 Oct 15, 2025
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch 3 times, most recently from 39c9f42 to 4573ee4 Compare October 16, 2025 07:37
@pmalek pmalek enabled auto-merge October 16, 2025 08:44
@pmalek pmalek added this pull request to the merge queue Oct 16, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 16, 2025
@renovate renovate bot force-pushed the renovate/cert-manager-cert-manager-1.x branch from 4573ee4 to 5b4fe69 Compare October 16, 2025 09:04
@programmer04 programmer04 added this pull request to the merge queue Oct 16, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 16, 2025
@programmer04 programmer04 added this pull request to the merge queue Oct 16, 2025
Merged via the queue into main with commit 82f6d13 Oct 16, 2025
69 of 92 checks passed
@programmer04 programmer04 deleted the renovate/cert-manager-cert-manager-1.x branch October 16, 2025 12:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants