[dependabot]

Bumps the cert-manager group with 1 update: github.com/cert-manager/cert-manager.

Updates github.com/cert-manager/cert-manager from 1.21.2 to 1.21.3

Release notes

Sourced from github.com/cert-manager/cert-manager's releases.

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

Commits

• 925c222 Merge pull request #9501 from wallrj-cyberark/release-1.21-go-1.26.10
• cfd6d18 Update vendored Go to 1.26.10
• c6746d7 Merge pull request #9495 from cert-manager/renovate/release-1.21-base-images
• a3ee670 chore(deps): update base images
• b3e26fb Merge pull request #9493 from cert-manager/renovate/release-1.21-base-images
• 6da0bf8 chore(deps): update base images
• 7c32f61 Merge pull request #9475 from cert-manager-bot/cherry-pick-9464-to-release-1.21
• 9d05ba7 Merge pull request #9474 from cert-manager-bot/cherry-pick-9467-to-release-1.21
• c7fef37 test(e2e): use local DNS zone for ACME webhook test
• 614e382 fixing ci tests with change in bind image
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions