Skip to content

Renovate: Update External dependencies#61

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/external-dependencies
Open

Renovate: Update External dependencies#61
renovate[bot] wants to merge 1 commit intomainfrom
renovate/external-dependencies

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 10, 2026

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/cert-manager/cert-manager v1.19.4v1.20.1 age adoption passing confidence
sigs.k8s.io/controller-runtime v0.23.1v0.23.3 age adoption passing confidence

Release Notes

cert-manager/cert-manager (github.com/cert-manager/cert-manager)

v1.20.1

Compare Source

v1.20.0

Compare Source

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

v1.20.0 adds alpha 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, @​jcpunk)
  • Added selectable fields to custom resource definitions for .spec.issuerRef.{group, kind, name} (#​8256, @​tareksha)
  • Added support for specifying imagePullSecrets in the startupapicheck-job Helm template to enable pulling images from private registries. (#​8186, @​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, @​dancmeyers)
  • Added parentRef override annotations on the Certificate resource. (#​8518, @​hjoshi123)
  • Added support for azure private zones for dns01 issuer. (#​8494, @​hjoshi123)
  • Added support for configuring PEM decoding size limits, allowing operators to handle larger certificates and keys. (#​7642, @​robertlestak)
  • Added support for unhealthyPodEvictionPolicy in PodDisruptionBudget (#​7728, @​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, @​k0da)
  • Improve error message when CA issuers are misconfigured to use a clashing secret name (#​8374, @​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, @​lunarwhite)
  • Update global.nodeSelector to helm chart to perform a merge and allow for a single nodeSelector to be set across all services. (#​8195, @​StingRayZA)
  • Vault issuers will now include the Vault server address as one of the default audiences on generated service account tokens. (#​8228, @​terinjokes)
  • Added experimental XListenerSets feature gate (#​8394, @​hjoshi123)
Documentation
Bug or Regression
  • Adds logs for cases when acme server returns us a fatal error in the order controller (#​8199, @​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, @​inteon)
  • Changes to the Duration and RenewBefore annotations on ingress and gateway-api resources will now trigger certificate updates. (#​8232, @​eleanor-merry)
  • Fix an issue where ACME challenge TXT records are not cleaned up when there are many resource records in CloudDNS. (#​8456, @​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, @​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, @​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, @​SlashNephy)
  • Fixed the HTTP-01 Gateway solver creating invalid HTTPRoutes by not setting spec.hostnames when the challenge DNSName is an IP address. (#​8443, @​alviss7)
  • Revert API defaults for issuer reference kind and group introduced in 0.19.0 (#​8173, @​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, @​SgtCoDFish)
  • Update Go to v1.25.5 to fix CVE-2025-61727 and CVE-2025-61729 (#​8290, @​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, @​LiquidPL)
Other (Cleanup or Flake)
kubernetes-sigs/controller-runtime (sigs.k8s.io/controller-runtime)

v0.23.3

Compare Source

What's Changed

Full Changelog: kubernetes-sigs/controller-runtime@v0.23.2...v0.23.3

v0.23.2

Compare Source

What's Changed

Full Changelog: kubernetes-sigs/controller-runtime@v0.23.1...v0.23.2


Configuration

📅 Schedule: Branch creation - "before 8am on Friday" (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 force-pushed the renovate/external-dependencies branch from e75ffec to 8c0c4a3 Compare March 10, 2026 15:43
@renovate renovate bot changed the title Renovate: Update module sigs.k8s.io/controller-runtime to v0.23.3 Renovate: Update External dependencies Mar 10, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 10, 2026

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 20 additional dependencies were updated

Details:

Package Change
k8s.io/api v0.35.0 -> v0.35.2
k8s.io/apimachinery v0.35.0 -> v0.35.2
k8s.io/client-go v0.35.0 -> v0.35.2
golang.org/x/crypto v0.48.0 -> v0.49.0
golang.org/x/net v0.51.0 -> v0.52.0
golang.org/x/oauth2 v0.34.0 -> v0.35.0
golang.org/x/sync v0.19.0 -> v0.20.0
golang.org/x/sys v0.41.0 -> v0.42.0
golang.org/x/term v0.40.0 -> v0.41.0
golang.org/x/text v0.34.0 -> v0.35.0
google.golang.org/genproto/googleapis/api v0.0.0-20251222181119-0a764e51fe1b -> v0.0.0-20260128011058-8636f8732409
google.golang.org/genproto/googleapis/rpc v0.0.0-20251222181119-0a764e51fe1b -> v0.0.0-20260319201613-d00831a3d3e7
google.golang.org/grpc v1.78.0 -> v1.79.3
k8s.io/apiextensions-apiserver v0.35.0 -> v0.35.2
k8s.io/apiserver v0.35.0 -> v0.35.2
k8s.io/component-base v0.35.0 -> v0.35.2
k8s.io/klog/v2 v2.130.1 -> v2.140.0
k8s.io/kube-openapi v0.0.0-20251125145642-4e65d59e963e -> v0.0.0-20260127142750-a19766b6e2d4
k8s.io/utils v0.0.0-20251222233032-718f0e51e6d2 -> v0.0.0-20260210185600-b8788abfbbc2
sigs.k8s.io/gateway-api v1.4.1 -> v1.5.0

@renovate renovate bot force-pushed the renovate/external-dependencies branch 3 times, most recently from 8e1ba4d to da2242f Compare March 16, 2026 07:08
@renovate renovate bot force-pushed the renovate/external-dependencies branch from da2242f to 5487c73 Compare March 27, 2026 21:39
@renovate renovate bot force-pushed the renovate/external-dependencies branch from 5487c73 to a0cd239 Compare April 1, 2026 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants