Update module github.com/cert-manager/cert-manager to v1.19.0 (main) - autoclosed #8428
+198
−234
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.18.2
->v1.19.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
cert-manager/cert-manager (github.com/cert-manager/cert-manager)
v1.19.0
Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
This release focuses on expanding platform compatibility, improving deployment flexibility, enhancing observability, and addressing key reliability issues.
Changes since
v1.18.0
:Feature
global.nodeSelector
to helm chart to allow for a singlenodeSelector
to be set across all services. (#7818, @StingRayZA)pathType
Exact
in ACME HTTP01 Ingress challenge solvers. (#7795, @sspreitzer)applyconfigurations
allowing clients to make type-safe server-side apply requests for cert-manager resources. (#7866, @erikgb)certmanager_certificate_challenge_status
Prometheus metric. (#7736, @hjoshi123)protocol
field forrfc2136
DNS01 provider (#7881, @hjoshi123)hostUsers
flag to all pods. Not set by default. (#7973, @hjoshi123)--acme-http01-solver-resource-*
settings. (#7972, @lunarwhite)CAInjectorMerging
feature has been promoted to BETA and is now enabled by default (#8017, @ThatsMrTalbot)certificate
metrics to the collector approach. (#7856, @hjoshi123)Bug or Regression
error waiting for authorization
(#7796, @hjoshi123)class
,ingressClassName
,name
) are specified simultaneously (#8021, @lunarwhite)global.rbac.disableHTTPChallengesRole
Helm option. (#7836, @inteon)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)ingress-nginx
in E2E tests to ensure compatibility (#7792, @wallrj)Other (Cleanup or Flake)
tokenrequest
RoleBinding resource to improve consistency (#7761, @lunarwhite)maps.Copy
for cleaner map handling (#8092, @quantpoet)vault-client-go
to the newvault/api
client. (#8059, @armagankaratosun)Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone Europe/Dublin, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.