AverageMarcus/cluster.fun
1
0 Fork 0
Code Issues 1 Pull Requests 4 Releases Activity

Update Helm release cert-manager to v1.21.3 #819

Merged
AverageMarcus merged 1 commits from renovate/cert-manager-1.x into master 2026-10-24 06:19:47 +00:00
Conversation 0 Commits 1 Files Changed 1
+1 -1
renovate commented 2026-10-24 03:33:30 +00:00
Collaborator
Copy link
Copy source

This PR contains the following updates:

Package Update Change
cert-manager (source) patch v1.21.2 → v1.21.3

Release Notes

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

v1.21.3

Compare Source

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

v1.21.3 removes trust in the compromised eMudhra CA (see eMudhra Compromise). The updated base images no longer include the "emSign ECC Root CA - G3" root certificate. Go 1.26.10 also makes crypto/x509 reject certificate chains that pass through the compromised intermediates (CVE-2026-111943).

It also fixes an ACME ARI renewal loop, stops the controller copying a private key from a Secret that the Certificate does not own, and quotes the proxy values in the Helm chart. It updates Go and several dependencies to fix reported security vulnerabilities.

All users should upgrade.

Changes by Kind

Bug or Regression
  • Added status.acme.ari.certID to track issuance of new certs and re-fetch ARI from CA. This fixes a renewal loop where a stale ARI window from the previous certificate triggered repeated re-issuance until the CA rate limit was hit. (#​9292, @​hjoshi123)
  • Helm chart: quote the http_proxy, https_proxy and no_proxy values when rendering the controller Deployment env vars, so values like *.example.com no longer break the manifest. (#​9407, @​pujitha24)
  • The requestmanager and issuing controllers now only consume the Secret named by status.nextPrivateKeySecretName when it carries the cert-manager.io/next-private-key label and is owned by the Certificate, matching the invariant the keymanager controller already enforces. Previously a principal able to write the certificates/status subresource, but not to read Secrets, could name any Secret in the namespace and have its private key copied into spec.secretName. The keymanager controller no longer creates the next private key Secret under the name in status.nextPrivateKeySecretName. It always uses a generated name, records a NotOwned Warning event when the field names a Secret it does not own, and repoints the field at the Secret it owns rather than deleting that Secret when the two disagree. The Secret named by spec.secretName is never treated as a next private key Secret, even if spec.secretTemplate labels it as one. (#​9368, @​wallrj)
Other (Cleanup or Flake)
  • Upgrade Go to 1.26.9, fixing CVEs in the crypto/tls, net/http, net/textproto and html/template packages. (#​9444, @​wallrj-cyberark)
  • Upgrade Go to 1.26.10, fixing a CVE in the crypto/x509 package. (#​9501, @​wallrj-cyberark)
  • Bump golang.org/x/net to v0.60.0 to fix reported security vulnerabilities (#​9451)
  • Bump go.opentelemetry.io/otel/exporters/otlp/otlptrace and otlptracegrpc to v1.45.0 to fix a reported security vulnerability (#​9374, #​9375)
  • Update distroless base images, removing the compromised "emSign ECC Root CA - G3" root certificate (#​9351, #​9414, #​9493, #​9495)

Configuration

📅 Schedule: (UTC)

  • 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 Mend Renovate CLI.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [cert-manager](https://cert-manager.io) ([source](https://github.com/cert-manager/cert-manager)) | patch | `v1.21.2` → `v1.21.3` | --- ### Release Notes <details> <summary>cert-manager/cert-manager (cert-manager)</summary> ### [`v1.21.3`](https://github.com/cert-manager/cert-manager/releases/tag/v1.21.3) [Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.21.2...v1.21.3) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.21.3 removes trust in the compromised eMudhra CA (see [eMudhra Compromise](https://cert-manager.io/docs/trust/trust-manager/#emudhra-compromise)). The updated base images no longer include the "emSign ECC Root CA - G3" root certificate. Go 1.26.10 also makes `crypto/x509` reject certificate chains that pass through the compromised intermediates ([CVE-2026-111943](https://pkg.go.dev/vuln/GO-2026-6809)). It also fixes an ACME ARI renewal loop, stops the controller copying a private key from a Secret that the Certificate does not own, and quotes the proxy values in the Helm chart. It updates Go and several dependencies to fix reported security vulnerabilities. All users should upgrade. #### Changes by Kind ##### Bug or Regression - Added `status.acme.ari.certID` to track issuance of new certs and re-fetch ARI from CA. This fixes a renewal loop where a stale ARI window from the previous certificate triggered repeated re-issuance until the CA rate limit was hit. ([#&#8203;9292](https://github.com/cert-manager/cert-manager/issues/9292), [@&#8203;hjoshi123](https://github.com/hjoshi123)) - Helm chart: quote the `http_proxy`, `https_proxy` and `no_proxy` values when rendering the controller Deployment env vars, so values like `*.example.com` no longer break the manifest. ([#&#8203;9407](https://github.com/cert-manager/cert-manager/issues/9407), [@&#8203;pujitha24](https://github.com/pujitha24)) - The `requestmanager` and `issuing` controllers now only consume the Secret named by `status.nextPrivateKeySecretName` when it carries the `cert-manager.io/next-private-key` label and is owned by the Certificate, matching the invariant the `keymanager` controller already enforces. Previously a principal able to write the `certificates/status` subresource, but not to read Secrets, could name any Secret in the namespace and have its private key copied into `spec.secretName`. The `keymanager` controller no longer creates the next private key Secret under the name in `status.nextPrivateKeySecretName`. It always uses a generated name, records a `NotOwned` Warning event when the field names a Secret it does not own, and repoints the field at the Secret it owns rather than deleting that Secret when the two disagree. The Secret named by `spec.secretName` is never treated as a next private key Secret, even if `spec.secretTemplate` labels it as one. ([#&#8203;9368](https://github.com/cert-manager/cert-manager/issues/9368), [@&#8203;wallrj](https://github.com/wallrj)) ##### Other (Cleanup or Flake) - Upgrade Go to 1.26.9, fixing CVEs in the crypto/tls, net/http, net/textproto and html/template packages. ([#&#8203;9444](https://github.com/cert-manager/cert-manager/issues/9444), [@&#8203;wallrj-cyberark](https://github.com/wallrj-cyberark)) - Upgrade Go to 1.26.10, fixing a CVE in the crypto/x509 package. ([#&#8203;9501](https://github.com/cert-manager/cert-manager/issues/9501), [@&#8203;wallrj-cyberark](https://github.com/wallrj-cyberark)) - Bump `golang.org/x/net` to v0.60.0 to fix reported security vulnerabilities ([#&#8203;9451](https://github.com/cert-manager/cert-manager/issues/9451)) - Bump `go.opentelemetry.io/otel/exporters/otlp/otlptrace` and `otlptracegrpc` to v1.45.0 to fix a reported security vulnerability ([#&#8203;9374](https://github.com/cert-manager/cert-manager/issues/9374), [#&#8203;9375](https://github.com/cert-manager/cert-manager/issues/9375)) - Update distroless base images, removing the compromised "emSign ECC Root CA - G3" root certificate ([#&#8203;9351](https://github.com/cert-manager/cert-manager/issues/9351), [#&#8203;9414](https://github.com/cert-manager/cert-manager/issues/9414), [#&#8203;9493](https://github.com/cert-manager/cert-manager/issues/9493), [#&#8203;9495](https://github.com/cert-manager/cert-manager/issues/9495)) </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xODEuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjE4MS4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->
renovate added 1 commit 2026-10-24 03:33:30 +00:00
Update Helm release cert-manager to v1.21.3 3f31deb6f5
AverageMarcus merged commit 03b6d55594 into master 2026-10-24 06:19:47 +00:00
AverageMarcus deleted branch renovate/cert-manager-1.x 2026-10-24 06:19:47 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
renovate (Renovate Bot) AverageMarcus (Marcus Noble)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: AverageMarcus/cluster.fun#819