fix(deps): update module github.com/cert-manager/cert-manager to v1.12.14 [security]

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/cert-manager/cert-manager	v1.8.0 → v1.12.14

GitHub Vulnerability Alerts

GHSA-r4pg-vg54-wxx4

Impact

cert-manager packages which call the standard library pem.Decode() function can take a long time to process specially crafted invalid PEM data.

If an attacker is able to modify PEM data which cert-manager reads (e.g. in a Secret resource), they may be able to use large amounts of CPU in the cert-manager controller pod to effectively create a denial-of-service (DoS) vector for cert-manager in the cluster.

Secrets are limited in size to 1MiB, which reduces the impact of this issue; it was discovered through an ~856kB fuzz test input which causes pem.Decode to take roughly 750ms to reject the input on an M2 Max Macbook Pro. By way of comparison, a valid PEM-encoded 4096-bit RSA key takes roughly 70µs to parse on the same machine.

Given the required size of PEM data needed to present a realistic DoS vector, an attacker would need to create or insert many different large sized resources in the cluster, and so the best secondary defense is to ensure that sensible limits are placed via RBAC.

This issue affects all versions of cert-manager to have been released since at least v0.1.0 (since pem.Decode is core functionality for cert-manager). All supported releases are patched.

Patches

The fixed versions are v1.16.2, v1.15.4 and v1.12.14.

• master branch: https://github.com/cert-manager/cert-manager/pull/7400
• release-1.16 branch: https://github.com/cert-manager/cert-manager/pull/7401
• release-1.15 branch: https://github.com/cert-manager/cert-manager/pull/7402
• release-1.12 branch: https://github.com/cert-manager/cert-manager/pull/7403

Workarounds

Ensure that RBAC is scoped correctly in your cluster. If a user is able to modify resources containing PEM data to be able to exploit this, it's like that those permissions are a bigger security threat than this issue - especially for Secret resources.

References

• Upstream issue: https://github.com/golang/go/issues/50116
• Similar issue: https://github.com/sigstore/sigstore/issues/198
• Google OSSFuzz: https://issues.oss-fuzz.com/issues/376728466

---

Release Notes

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

v1.12.14

Compare Source

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

This patch release of cert-manager 1.12 makes several changes to how PEM input is validated, adding maximum sizes appropriate to the type of PEM data which is being parsed.

This is to prevent an unacceptable slow-down in parsing specially crafted PEM data. The issue was found by Google's OSS-Fuzz project.

The issue is low severity; to exploit the PEM issue would require privileged access which would likely allow Denial-of-Service through other methods.

Note also that since most PEM data parsed by cert-manager comes from ConfigMap or Secret resources which have a max size limit of approximately 1MB, it's difficult to force cert-manager to parse large amounts of PEM data.

Further information is available in GHSA-r4pg-vg54-wxx4

This patch release also fix an issue reported by Trivy, although that issue is low severity and is not expected to be relevant to cert-manager.

Bug Fixes

• Set a maximum size for PEM inputs which cert-manager will accept to remove possibility of taking a long time to process an input (#​7403, @​SgtCoDFish)
• Fix CVE-2024-5174 in github.com/golang-jwt/jwt/v4 (#​7407, @​SgtCoDFish)

v1.12.13

Compare Source

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

📖 Read the release documentation to learn more more about the features introduced in 1.12.

📜 Changes since v1.12.12

This patch release fixes the following vulnerabilities: CVE-2024-6104, CVE-2024-24791, CVE-2024-25620, CVE-2024-26147, and CVE-2024-41110.

ℹ️ This version contains an unusually large number of Go dependency changes for
a patch release. The cert-manager maintainers are confident that it is stable
because it has passed the same extensive suite of tests as previous 1.12
releases. But if you are importing cert-manager 1.12 as a Go module you will
notice that the minimum Go version is 1.21, and the k8s.io modules are now
updated to 0.29.

This reason for the large number of Go dependency changes is that the Helm SDK
has been updated to fix security vulnerabilities in cmctl. This required the
k8s.io modules to be updated from 0.27 to 0.29 in all components. Those
newer minor versions of the Kubernetes modules pulled in new transitive
dependencies, and incremented the minimum Go version from 1.20 to 1.21.

Bugfixes

• Bump the go-retryablehttp dependency to fix CVE-2024-6104 (#​7128, @​SgtCoDFish)
• Updated Helm dependency to resolve CVE-2024-25620 and CVE-2024-26147 and Docker dependency to resolve CVE-2024-41110 (#​7214, @​ThatsMrTalbot)
• Updates Go to 1.21.13 to resolve CVE-2024-24791 (#​7216, @​ThatsMrTalbot)

v1.12.12

Compare Source

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

📜 Changes since v1.12.11

Bugfixes

• BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#​7114, @​cert-manager-bot)

Other (Cleanup or Flake)

• Upgrade go-jose library to fix CVE-2024-28180 trivy alert. (#​7109, @​inteon)
• Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to address CVE-2024-35255 (#​7099, @​ThatsMrTalbot)

v1.12.11

Compare Source

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

📜 Changes since v1.12.10

Other (Cleanup or Flake)

• Updated Go to 1.21.11 bringing in security fixes for archive/zip and net/netip. (#​7077, @​ThatsMrTalbot )
• Upgrade Go to 1.21.10, fixing GO-2024-2824 (GHSA-2jwv-jmq4-4j3r). (#​7010, @​inteon)

v1.12.10

Compare Source

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

v1.12.10 fixes a bug in the DigitalOcean DNS-01 provider which could cause incorrect DNS records to be deleted when using a domain with a CNAME. Special thanks to @​BobyMCbobs for reporting this issue and testing the fix!

It also patches CVE-2023-45288.

⚠️ Known Issues

• ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see release docs for more info and mitigations

• If you misconfigure two Certificate resources to have the same target Secret resource, cert-manager will generate a MANY CertificateRequests, possibly causing high CPU usage and/ or high costs due to the large number of certificates issued (see #​6406).
  This problem was resolved in v1.13.2 and other later versions, but the fix cannot be easily backported to v1.12.x. We recommend using v1.12.x with caution (avoid misconfigured Certificate resources) or upgrading to a newer version.

Changes

Bug or Regression

• DigitalOcean: Ensure that only TXT records are considered for deletion when cleaning up after an ACME challenge (#​6894, @​SgtCoDFish)
• Bump golang.org/x/net to address CVE-2023-45288 (#​6933, @​SgtCoDFish)

v1.12.9

Compare Source

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

⚠️ Known Issues

• ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see release docs for more info and mitigations

• If you misconfigure two Certificate resources to have the same target Secret resource, cert-manager will generate a MANY CertificateRequests, possibly causing high CPU usage and/ or high costs due to the large number of certificates issued (see #​6406).
  This problem was resolved in v1.13.2 and other later versions, but the fix cannot be easily backported to v1.12.x. We recommend using v1.12.x with caution (avoid misconfigured Certificate resources) or upgrading to a newer version.

ℹ️ Documentation

Release notes
Upgrade notes
Installation instructions

🔧 Breaking changes

See Breaking changes in v1.12.0 release notes

📜 Changes since v1.12.8

Bug or Regression

• Allow cert-manager.io/allow-direct-injection in annotations (#​6811, @​jetstack-bot)
• BUGFIX: JKS and PKCS12 stores now contain the full set of CAs specified by an issuer (#​6813, @​inteon)
• BUGFIX: fix race condition due to registering and using global runtime.Scheme variables (#​6833, @​inteon)

Other (Cleanup or Flake)

• Bump base images to the latest version. (#​6843, @​jetstack-bot)
• Upgrade go to 1.21.8: fixes CVE-2024-24783 (#​6826, @​jetstack-bot)
• Upgrade google.golang.org/protobuf: fixing GO-2024-2611 (#​6830, @​inteon)

v1.12.8

Compare Source

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

⚠️ Known Issues

• ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see release docs for more info and mitigations

• If you misconfigure two Certificate resources to have the same target Secret resource, cert-manager will generate a MANY CertificateRequests, possibly causing high CPU usage and/ or high costs due to the large number of certificates issued (see #​6406).
  This problem was resolved in v1.13.2 and other later versions, but the fix cannot be easily backported to v1.12.x. We recommend using v1.12.x with caution (avoid misconfigured Certificate resources) or upgrading to a newer version.

ℹ️ Documentation

Release notes
Upgrade notes
Installation instructions

🔧 Breaking changes

See Breaking changes in v1.12.0 release notes

📜 Changes since v1.12.7

Bug or Regression

• BUGFIX: LiteralSubjects with a #= value can result in memory issues due to faulty BER parser (github.com/go-asn1-ber/asn1-ber). (#​6773, @​jetstack-bot)

Other (Cleanup or Flake)

• Bump go to 1.20.14 (#​6733, @​SgtCoDFish)
• Cert-manager is now built with Go 1.20.13 (#​6629, @​SgtCoDFish)
• Fix CVE 2023 48795 by upgrading to golang.org/x/crypto@​v0.17.0 (#​6678, @​wallrj)
• Fix GHSA-7ww5-4wqc-m92c by upgrading to github.com/containerd/containerd@v1.7.12 (#​6689, @​wallrj)

v1.12.7

Compare Source

This patch release contains fixes for the following security vulnerabilities in the cert-manager-controller:

• GO-2023-2382: Denial of service via chunk extensions in net/http

If you use ArtifactHub Security report or trivy, this patch will also silence the following warning about a vulnerability in code which is imported but not used by the cert-manager-controller:

• CVE-2023-47108: DoS vulnerability in otelgrpc due to unbound cardinality metrics.

An ongoing security audit of cert-manager suggested some changes to the webhook code to mitigate DoS attacks,
and these are included in this patch release.

Known bugs

If you misconfigure two Certificate resources to have the same target Secret resource, cert-manager will generate a MANY CertificateRequests, possibly causing high CPU usage and/ or high costs due to the large number of certificates issued (see #​6406).

This problem was resolved in v1.13.2 and other later versions, but the fix cannot be easily backported to v1.12.x. We recommend using v1.12.x with caution (avoid misconfigured Certificate resources) or upgrading to a newer version.

Changes

Feature

• cert-manager is now built with Go 1.20.12 (#​6543, @​wallrj).

Bug or Regression

• The webhook server now returns HTTP error 413 (Content Too Large) for requests with body size >= 3MiB. This is to mitigate DoS attacks that attempt to crash the webhook process by sending large requests that exceed the available memory (#​6506, @​inteon).
• The webhook server now returns HTTP error 400 (Bad Request) if the request contains an empty body (#​6506, @​inteon).
• The webhook server now returns HTTP error 500 (Internal Server Error) rather than crashing, if the code panics while handling a request (#​6506, @​inteon).
• Mitigate potential Slowloris attacks by setting ReadHeaderTimeout in all http.Server instances (#​6539, @​wallrj).
• Upgrade otel and docker to fix: CVE-2023-47108 and GHSA-jq35-85cj-fj4p (#​6513, @​inteon).

Dependencies

Added

• cloud.google.com/go/dataproc/v2: v2.0.1

Changed

• cloud.google.com/go/aiplatform: v1.45.0 → v1.48.0
• cloud.google.com/go/analytics: v0.21.2 → v0.21.3
• cloud.google.com/go/baremetalsolution: v0.5.0 → v1.1.1
• cloud.google.com/go/batch: v0.7.0 → v1.3.1
• cloud.google.com/go/beyondcorp: v0.6.1 → v1.0.0
• cloud.google.com/go/bigquery: v1.52.0 → v1.53.0
• cloud.google.com/go/cloudbuild: v1.10.1 → v1.13.0
• cloud.google.com/go/cloudtasks: v1.11.1 → v1.12.1
• cloud.google.com/go/compute: v1.21.0 → v1.23.0
• cloud.google.com/go/contactcenterinsights: v1.9.1 → v1.10.0
• cloud.google.com/go/container: v1.22.1 → v1.24.0
• cloud.google.com/go/datacatalog: v1.14.1 → v1.16.0
• cloud.google.com/go/dataplex: v1.8.1 → v1.9.0
• cloud.google.com/go/datastore: v1.12.1 → v1.13.0
• cloud.google.com/go/datastream: v1.9.1 → v1.10.0
• cloud.google.com/go/deploy: v1.11.0 → v1.13.0
• cloud.google.com/go/dialogflow: v1.38.0 → v1.40.0
• cloud.google.com/go/documentai: v1.20.0 → v1.22.0
• cloud.google.com/go/eventarc: v1.12.1 → v1.13.0
• cloud.google.com/go/firestore: v1.11.0 → v1.12.0
• cloud.google.com/go/gkebackup: v0.4.0 → v1.3.0
• cloud.google.com/go/gkemulticloud: v0.6.1 → v1.0.0
• cloud.google.com/go/kms: v1.12.1 → v1.15.0
• cloud.google.com/go/maps: v0.7.0 → v1.4.0
• cloud.google.com/go/metastore: v1.11.1 → v1.12.0
• cloud.google.com/go/policytroubleshooter: v1.7.1 → v1.8.0
• cloud.google.com/go/pubsub: v1.32.0 → v1.33.0
• cloud.google.com/go/run: v0.9.0 → v1.2.0
• cloud.google.com/go/servicedirectory: v1.10.1 → v1.11.0
• cloud.google.com/go/speech: v1.17.1 → v1.19.0
• cloud.google.com/go/translate: v1.8.1 → v1.8.2
• cloud.google.com/go/video: v1.17.1 → v1.19.0
• cloud.google.com/go/vmwareengine: v0.4.1 → v1.0.0
• cloud.google.com/go: v0.110.4 → v0.110.7
• github.com/felixge/httpsnoop: v1.0.3 → v1.0.4
• github.com/go-logr/logr: v1.2.4 → v1.3.0
• github.com/golang/glog: v1.1.0 → v1.1.2
• github.com/google/go-cmp: v0.5.9 → v0.6.0
• github.com/google/uuid: v1.3.0 → v1.3.1
• go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc: v0.45.0 → v0.46.0
• go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp: v0.44.0 → v0.46.0
• go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc: v1.19.0 → v1.20.0
• go.opentelemetry.io/otel/exporters/otlp/otlptrace: v1.19.0 → v1.20.0
• go.opentelemetry.io/otel/metric: v1.19.0 → v1.20.0
• go.opentelemetry.io/otel/sdk: v1.19.0 → v1.20.0
• go.opentelemetry.io/otel/trace: v1.19.0 → v1.20.0
• go.opentelemetry.io/otel: v1.19.0 → v1.20.0
• go.uber.org/goleak: v1.2.1 → v1.3.0
• golang.org/x/oauth2: v0.10.0 → v0.11.0
• golang.org/x/sys: v0.13.0 → v0.14.0
• google.golang.org/genproto/googleapis/api: 782d3b1 → b8732ec
• google.golang.org/genproto/googleapis/rpc: 782d3b1 → b8732ec
• google.golang.org/genproto: 782d3b1 → b8732ec
• google.golang.org/grpc: v1.58.3 → v1.59.0

Removed

• cloud.google.com/go/dataproc: v1.12.0

v1.12.6

Compare Source

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

v1.12.6 fixes some CVE alerts and a Venafi issuer bug.

Known bugs

If you misconfigure two Certificate resources to have the same target Secret resource, cert-manager will generate a MANY CertificateRequests, possibly causing high CPU usage and/ or high costs due to the large number of certificates issued (see #​6406).

This problem was resolved in v1.13.2 and other later versions, but the fix cannot be easily backported to v1.12.x. We recommend using v1.12.x with caution (avoid misconfigured Certificate resources) or upgrading to a newer version.

Changes since v1.12.5

Bug or Regression

• Bump golang.org/x/net v0.15.0 => v0.17.0 as part of addressing CVE-2023-44487 / CVE-2023-39325 (#​6431, @​SgtCoDFish)
• The Venafi issuer now properly resets the certificate and should no longer get stuck with WebSDK CertRequest Module Requested Certificate or This certificate cannot be processed while it is in an error state. Fix any errors, and then click Retry.. (#​6401, @​maelvls)

Other (Cleanup or Flake)

• Bump go to 1.20.10 to address CVE-2023-39325. Also bumps base images. (#​6412, @​SgtCoDFish)

v1.12.5

Compare Source

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

v1.12.5 contains a backport for a name collision bug that was found in v1.13.0

Changes since v1.12.4

Bug or Regression

• BUGFIX: fix CertificateRequest name collision bug in StableCertificateRequestName feature. (#​6359, @​jetstack-bot)

Other (Cleanup or Flake)

• Updated base images to the latest version. (#​6372, @​inteon)
• Upgrade Go from 1.20.7 to 1.20.8. (#​6371, @​jetstack-bot)

v1.12.4

Compare Source

v1.12.4 contains an important security fix that addresses CVE-2023-29409.

Changes since v1.12.3

• Fixes an issue where cert-manager would incorrectly reject two IP addresses as being unequal when they should have compared equal. This would be most noticeable when using an IPv6 address which doesn't match how Go's net.IP.String() function would have printed that address. (#​6297, @​SgtCoDFish)
• Use Go 1.20.7 to fix a security issue in Go's crypto/tls library. (#​6318, @​maelvls)

v1.12.3

Compare Source

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

v1.12.3 contains a bug fix for the cainjector which addresses a memory leak!

Changes since v1.12.2

Bugfixes

• BUGFIX[cainjector]: 1-character bug was causing invalid log messages and a memory leak (#​6235, @​jetstack-bot)

v1.12.2

Compare Source

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

v1.12.2 is a bugfix release, but includes a known issue and you should prefer the latest patch release!

Known issues

⚠️ cert-manager v1.12.0, v1.12.1 and v1.12.2 all have known issues. You should install the latest patch release of v1.12 and skip over the affected versions.

• cainjector contains a memory leak in v1.12.0, v1.12.1 and v1.12.2 due to re-assignment of a log variable (see #​6217). The fix was released in v1.12.3. See #​6232 for further context.

Changes since v1.12.1

Bugfixes

• BUGFIX: cmctl check api --wait 0 exited without output; we now make sure we perform the API check at least once (#​6116, @​jetstack-bot)

v1.12.1

Compare Source

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

v1.12.1 release contains a couple dependency bumps and changes to ACME external webhook library.

Known issues

⚠️ cert-manager v1.12.0, v1.12.1 and v1.12.2 all have known issues. You should install the latest patch release of v1.12 and skip over the affected versions.

• cmctl API check is broken in v1.12.0 and v1.12.1. We suggest that you do not upgrade cmctl to this version. The fix was released in v1.12.2 (which has an additional issue, see below). See #​6116 for context.
• cainjector contains a memory leak in v1.12.0, v1.12.1 and v1.12.2 due to re-assignment of a log variable (see #​6217). The fix was released in v1.12.3. See #​6232 for further context.

Changes since v1.12.0

Other (Cleanup or Flake)

• Don't run API Priority and Fairness controller in webhook's extension apiserver (#​6085, @​irbekrm)
• Adds a warning for folks to not use controller feature gates helm value to configure webhook feature gates (#​6100, @​irbekrm)

Uncategorized

• Updates Kubernetes libraries to v0.27.2. (#​6077, @​lucacome)
• Updates controller-runtime to v0.15.0 (#​6098, @​lucacome)

v1.12.0

Compare Source

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

cert-manager v1.12 brings support for JSON logging, a lower memory footprint, support for ephemeral service account tokens with Vault, improved dependency management and support for the ingressClassName field.

The full release notes are available at https://cert-manager.io/docs/release-notes/release-notes-1.12.

Known issues

⚠️ cert-manager v1.12.0, v1.12.1 and v1.12.2 all have known issues. You should install the latest patch release of v1.12 and skip over the affected versions.

• cmctl API check is broken in v1.12.0 and v1.12.1. We suggest that you do not upgrade cmctl to this version. The fix was released in v1.12.2 (which has an additional issue, see below). See #​6116 for context.
• cainjector contains a memory leak in v1.12.0, v1.12.1 and v1.12.2 due to re-assignment of a log variable (see #​6217). The fix was released in v1.12.3. See #​6232 for further context.

Community

Thanks again to all open-source contributors with commits in this release, including:

• @​malovme
• @​e96wic
• @​ExNG
• @​waterfoul
• @​jkroepke
• @​andrewsomething
• @​yulng
• @​tobotg
• @​maumontesilva
• @​avi-08
• @​vinzent
• @​TrilokGeer
• @​g-gaston
• @​james-callahan
• @​lucacome
• @​yanggangtony
• @​vidarno
• @​ctrought
• @​Robfz
• @​dsonck92
• @​rayandas
• @​olekfur
• @​ptrc-n
• @​bradjones1
• @​gdvalle

Thanks also to the following cert-manager maintainers for their contributions during this release:

• @​inteon
• @​wallrj
• @​maelvls
• @​SgtCoDFish
• @​irbekrm
• @​jakexks
• @​JoshVanL
• @​munnerz

Equally thanks to everyone who provided feedback, helped users and raised issues on Github and Slack, joined our meetings and talked to us at Kubecon!

Special thanks to @​erikgb for continuously great input and feedback and to @​lucacome for always ensuring that our kube deps are up to date!

Thanks also to the CNCF, which provides resources and support, and to the AWS open source team for being good community members and for their maintenance of the PrivateCA Issuer.

In addition, massive thanks to Jetstack (by Venafi) for contributing developer time and resources towards the continued maintenance of cert-manager projects.

Changes by Kind

Feature

• POTENTIALLY BREAKING: the cert-manager binaries and some tests have been split into separate Go modules, allowing them to be easily patched independently. This should have no impact if you simply run cert-manager in your cluster. If you import cert-manager binaries, integration tests or end-to-end tests in Go, you may need to make code changes in response to this. See https://cert-manager.io/docs/contributing/importing/ for more details. (#​5880, @​SgtCoDFish)
• Added support for JSON logging (using --logging-format=json) (#​5828, @​malovme)
• Added the --concurrent-workers flag that lets you control the number of concurrent workers for each of our controllers. (#​5936, @​inteon)
• Adds acme.solvers.http01.ingress.podTemplate.spec.imagePullSecrets field to issuer spec to allow to specify image pull secrets for the ACME HTTP01 solver pod. (#​5801, @​malovme)
• Cainjector:
  • New flags were added to the cainjector binary. They can be used to modify what injectable kinds are enabled. If cainjector is only used as a cert-manager's internal component it is sufficient to only enable validatingwebhookconfigurations and mutatingwebhookconfigurations injectable resources; disabling the rest can improve memory consumption. By default all are enabled.
  • The --watch-certs flag was renamed to --enable-certificates-data-source. (#​5766, @​irbekrm)
• Helm: Added PodDisruptionBudgets for cert-manager components to the Helm chart (disabled by default). (#​3931, @​e96wic)
• Helm: Egress 6443/TCP is now allowed in the webhook. This is required for OpenShift and OKD clusters for which the Kubernetes API server listens on port 6443 instead of 443. (#​5788, @​ExNG)
• Helm: you can now add volumes and volume mounts via Helm variables for the cainjector, webhook, and startupapicheck. (#​5668, @​waterfoul)
• Helm: you can now enable the flags --dns01-recursive-nameservers, --enable-certificate-owner-ref, and --dns01-recursive-nameservers-only through Helm values. (#​5614, @​jkroepke)
• The DigitalOcean issuer now sets a cert-manager user agent string. (#​5869, @​andrewsomething)
• The HTTP-01 solver can now be configured to create Ingresses with an ingressClassName. The credit goes to @​dsonck92 for implementing the initial PR. (#​5849, @​maelvls)
• The Vault issuer can now be used with ephemeral Kubernetes tokens. With the new serviceAccountRef field, cert-manager generates a short-lived token associated to the service account to authenticate to Vault. Along with this new feature, we have added validation logic in the webhook in order to check the vault.auth field when creating an Issuer or ClusterIssuer. Previously, it was possible to create an Issuer or ClusterIssuer with an invalid value for vault.auth. (#​5502, @​maelvls)
• The cert-manager controller container of the controller Pod now has a /livez endpoint and a default liveness probe, which fails if leader election has been lost and for some reason the process has not exited. The liveness probe is disabled by default. (#​5962, @​wallrj)
• Upgraded Gateway API to v0.6.0. (#​5768, @​yulng)
• Webhook now logs requests to mutating/validating webhook (with --v=5 flag) (#​5975, @​tobotg)

Design

• Certificate issuances are always failed (and retried with a backoff) for denied or invalid CertificateRequests.
  This is not necessarily a breaking change as due to a race condition this may already have been the case. (#​5887, @​irbekrm)
• The cainjector controller can now use server-side apply to patch mutatingwebhookconfigurations, validatingwebhookconfigurations, apiservices, and customresourcedefinitions. This feature is currently in alpha and is not enabled by default. To enable server-side apply for the cainjector, add the flag --feature-gates=ServerSideApply=true to the deployment. (#​5991, @​inteon)

Documentation

• Helm: the dead links in values.yaml are now working (#​5999, @​SgtCoDFish)

Bug or Regression

• Cmctl renew now prints an error message unless Certificate name(s) or --all are supplied (#​5896, @​maumontesilva)
• Cmctl: In order work around a hardcoded Kubernetes version in Helm, we now use a fake kube-apiserver version when generating the helm template when running cmctl x install. (#​5720, @​irbekrm)
• Fix development environment and go vendoring on Linux arm64. (#​5810, @​SgtCoDFish)
• Fix ordering of remote git tags when preparing integration tests (#​5910, @​SgtCoDFish)
• Helm: the flag --acme-http01-solver-image given to the variable acmesolver.extraArgs now has precedence over the variable acmesolver.image. (#​5693, @​SgtCoDFish)
• Ingress and Gateway resources will not be synced if deleted via foreground cascading. (#​5878, @​avi-08)
• The auto-retry mechanism added in VCert 4.23.0 and part of cert-manager 1.11.0 (#​5674) has been found to be faulty. Until this issue is fixed upstream, we now use a patched version of VCert. This patch will slowdown the issuance of certificates by 9% in case of heavy load on TPP. We aim to release at an ulterior date a patch release of cert-manager to fix this slowdown. (#​5805, @​inteon)
• Upgrade to go 1.19.6 along with newer helm and containerd versions and updated base images (#​5813, @​SgtCoDFish)
• When using the jks and pkcs12 fields on a Certificate resource with a CA issuer that doesn't set the ca.crt in the Secret resource, cert-manager no longer loop trying to copy ca.crt into truststore.jks or truststore.p12. (#​5972, @​vinzent)
• When using the literalSubject field on a Certificate resource, the IPs, URIs, DNS names, and email addresses segments are now properly compared. (#​5747, @​inteon)

Other (Cleanup or Flake)

• ACME account registration is now re-verified if account key is manually changed. (#​5949, @​TrilokGeer)
• Add make go-workspace target for generating a go.work file for local development (#​5935, @​SgtCoDFish)
• Added a Makefile target to build a standalone E2E test binary: make e2e-build (#​5804, @​wallrj)
• Bump keystore-go to v4.4.1 to work around an upstream rewrite of history (#​5724, @​g-gaston)
• Bump the distroless base images (#​5929, @​maelvls)
• Bumps base images (#​5793, @​irbekrm)
• Cainjector memory improvements: removes second cache of secrets, CRDs, validating/mutatingwebhookconfigurations and APIServices that should reduce memory consumption by about half.
  **BREAKING:*- users who are relying on cainjector to work when certificates.cert-manager.io CRD is not installed in the cluster, now need to pass --watch-certificates=false flag to cainjector else it will not start.
  Users who only use cainjector as cert-manager's internal component and have a large number of Certificate resources in cluster can pass --watch-certificates=false to avoid cainjector from caching Certificate resources and save some memory. (#​5746, @​irbekrm)
• Cainjector now only reconciles annotated objects of injectable kind. (#​5764, @​irbekrm)
• Container images are have an OCI source label (#​5722, @​james-callahan)
• Enable cmctl to be imported by third parties (#​6050, @​jetstack-bot)
• The acmesolver pods created by cert-manager now have automountServiceAccountToken turned off. (#​5754, @​wallrj)
• The controller binary now uses much less memory on Kubernetes clusters with large or numerous Secret resources. The controller now ignores the contents of Secrets that aren't relevant to cert-manager. This functionality is currently placed behind SecretsFilteredCaching feature flag. The filtering mechanism might, in some cases, slightly slow down issuance or cause additional requests to kube-apiserver because unlabelled Secret resources that cert-manager controller needs will now be retrieved from kube-apiserver instead of being cached locally. To prevent this from happening, users can label all issuer Secret resources with the controller.cert-manager.io/fao: true label. (#​5824, @​irbekrm)
• The controller memory usage has been further decreased by ignoring annotations, labels and managed fields when caching Secret resources. (#​5966, @​irbekrm)
• The controller now makes fewer calls to the ACME server.
  POTENTIALLY BREAKING: this PR slightly changes how the name of the Challenge resources are calculated. To avoid duplicate issuances due to the Challenge resource being recreated, ensure that there is no in-progress ACME certificate issuance when you upgrade to this version of cert-manager. (#​5901, @​irbekrm)
• The memory usage of the controller has been reduced by only caching the metadata of Pods and Services. (#​5976, @​irbekrm)
• The number of calls made to the ACME server during the controller startup has been reduced by storing the private key hash in the Issuer's status. (#​6006, @​vidarno)
• Updates Kubernetes libraries to v0.26.2. (#​5820, @​lucacome)
• Updates Kubernetes libraries to v0.26.3. (#​5907, @​lucacome)
• Updates Kubernetes libraries to v0.27.1. (#​5961, @​lucacome)
• Updates base images (#​5832, @​irbekrm)
• Upgrade to Go 1.20 (#​5969, @​wallrj)
• Upgrade to go 1.19.5 (#​5712, @​yanggangtony)
• Validates that certificate.spec.secretName is a valid Secret name (#​5967, @​avi-08)
• We are now testing with Kubernetes v1.27.1 by default. (#​5979, @​irbekrm)
• certificate.spec.secretName Secrets will now be labelled with controller.cert-manager.io/fao label (#​5660, @​irbekrm)

Uncategorized

• We have replaced our python boilerplate checker with an installed Go version, removing the need to have Python installed when developing or building cert-manager. (#​6000, @​SgtCoDFish)

v1.11.5

Compare Source

v1.11.5 contains an important security fix that addresses CVE-2023-29409.

Changes since v1.11.4

• Use Go 1.19.9 to fix a security issue in Go's crypto/tls library. (#​6317, @​maelvls)

v1.11.4

Compare Source

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

cert-manager v1.11.4 contains some version bumps to address reported CVEs (although we don't expect that cert-manager was actually vulnerable to anything!)

Changes by Kind

Other (Cleanup or Flake)

• Resolved docker/docker trivy CVE alert (#​6164, @​inteon)
• Upgraded base images (#​6128, @​SgtCoDFish)

Dependencies

Changed

• github.com/docker/distribution: v2.8.1+incompatible → v2.8.2+incompatible

v1.11.3

Compare Source

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

v1.11.3 mostly contains ACME library changes. API Priority and Fairness feature is now disabled in the external webhook's extension apiserver.

Changes by Kind

Other (Cleanup or Flake)

• API Priority and Fairness controller is now disabled in extension apiserver for DNS webhook implementation. (#​6092, @​irbekrm)
• Adds a warning for folks to not use controller feature gates helm value to configure webhook feature gates (#​6101, @​irbekrm)

v1.11.2

Compare Source

Changelog since v1.11.1

Changes by Kind

Bug or Regression

• Build with go 1.19.9 (#​6014, @​SgtCoDFish)

Other (Cleanup or Flake)

• Bump the distroless base images (#​5930, @​maelvls)

• Bumps Docker libraries to fix vulnerability scan alert for CVE-2023-28840, CVE-2023-28841, CVE-2023-28842 (#​6037, @​irbekrm)
  Cert-manager was not actually affected by these CVEs which are all to do with Docker daemon's overlay network.

• Bumps Kube libraries v0.26.0 -> v0.26.4 (#​6038, @​irbekrm)
  This might help with running cert-manager v1.11 on Kubernetes v1.27, see #​6038

v1.11.1

Compare Source

cert-manager is the easiest way to automat

---

Configuration

📅 Schedule: Branch creation - "" (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.

🔕 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]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum

Command failed: go get -t ./...
go: downloading github.com/cert-manager/cert-manager v1.12.14
go: downloading github.com/sirupsen/logrus v1.9.3
go: downloading k8s.io/client-go v0.29.7
go: downloading k8s.io/apiextensions-apiserver v0.29.7
go: downloading k8s.io/apimachinery v0.29.7
go: downloading k8s.io/component-base v0.29.7
go: downloading golang.org/x/sys v0.21.0
go: downloading golang.org/x/net v0.26.0
go: downloading k8s.io/klog/v2 v2.110.1
go: downloading k8s.io/utils v0.0.0-20230726121419-3b25d923346b
go: downloading sigs.k8s.io/structured-merge-diff/v4 v4.4.1
go: downloading github.com/spf13/cobra v1.8.0
go: downloading k8s.io/apiserver v0.29.7
go: downloading github.com/go-logr/logr v1.3.0
go: downloading golang.org/x/term v0.21.0
go: downloading golang.org/x/oauth2 v0.11.0
go: downloading golang.org/x/time v0.3.0
go: downloading sigs.k8s.io/json v0.0.0-20221116044647-bc3834ca7abd
go: downloading github.com/inconshreveable/mousetrap v1.1.0
go: downloading github.com/coreos/go-systemd/v22 v22.5.0
go: downloading github.com/emicklei/go-restful/v3 v3.11.0
go: downloading github.com/evanphx/json-patch v5.7.0+incompatible
go: downloading github.com/google/uuid v1.6.0
go: downloading golang.org/x/crypto v0.24.0
go: downloading k8s.io/api v0.29.7
go: downloading k8s.io/kube-openapi v0.0.0-20231010175941-2dd684a91f00
go: downloading go.opentelemetry.io/otel v1.20.0
go: downloading go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.20.0
go: downloading go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.20.0
go: downloading go.opentelemetry.io/otel/sdk v1.20.0
go: downloading google.golang.org/grpc v1.59.0
go: downloading gopkg.in/natefinch/lumberjack.v2 v2.2.1
go: downloading k8s.io/kube-aggregator v0.29.7
go: downloading github.com/google/go-cmp v0.6.0
go: downloading golang.org/x/text v0.16.0
go: downloading github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc
go: downloading github.com/google/cel-go v0.17.7
go: downloading go.opentelemetry.io/otel/trace v1.20.0
go: downloading go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.46.0
go: downloading github.com/fsnotify/fsnotify v1.7.0
go: downloading sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.28.0
go: downloading github.com/golang/protobuf v1.5.4
go: downloading github.com/google/gnostic-models v0.6.8
go: downloading github.com/go-openapi/swag v0.22.3
go: downloading github.com/go-openapi/jsonreference v0.20.2
go: downloading go.opentelemetry.io/proto/otlp v1.0.0
go: downloading google.golang.org/genproto v0.0.0-20230822172742-b8732ec3820d
go: downloading google.golang.org/genproto/googleapis/rpc v0.0.0-20230822172742-b8732ec3820d
go: downloading k8s.io/kms v0.29.7
go: downloading go.etcd.io/etcd/client/pkg/v3 v3.5.10
go: downloading go.etcd.io/etcd/client/v3 v3.5.10
go: downloading go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.46.0
go: downloading go.uber.org/zap v1.24.0
go: downloading github.com/imdario/mergo v0.3.13
go: downloading sigs.k8s.io/gateway-api v0.7.0
go: downloading github.com/go-logr/zapr v1.2.4
go: downloading gopkg.in/yaml.v3 v3.0.1
go: downloading google.golang.org/genproto/googleapis/api v0.0.0-20230822172742-b8732ec3820d
go: downloading google.golang.org/protobuf v1.33.0
go: downloading github.com/stoewer/go-strcase v1.2.0
go: downloading golang.org/x/sync v0.7.0
go: downloading github.com/blang/semver/v4 v4.0.0
go: downloading github.com/prometheus/client_golang v1.16.0
go: downloading github.com/prometheus/client_model v0.4.0
go: downloading github.com/prometheus/procfs v0.10.1
go: downloading github.com/felixge/httpsnoop v1.0.4
go: downloading go.opentelemetry.io/otel/metric v1.20.0
go: downloading github.com/mailru/easyjson v0.7.7
go: downloading github.com/go-openapi/jsonpointer v0.19.6
go: downloading github.com/cenkalti/backoff/v4 v4.2.1
go: downloading github.com/grpc-ecosystem/grpc-gateway/v2 v2.16.0
go: downloading go.etcd.io/etcd/api/v3 v3.5.10
go: downloading go.uber.org/atomic v1.10.0
go: downloading go.uber.org/multierr v1.11.0
go: downloading github.com/antlr/antlr4/runtime/Go/antlr/v4 v4.0.0-20230305170008-8188dc5388df
go: downloading github.com/asaskevich/govalidator v0.0.0-20200428143746-21a406dcc535
go: downloading github.com/cespare/xxhash/v2 v2.2.0
go: downloading github.com/prometheus/common v0.44.0
go: downloading github.com/go-logr/stdr v1.2.2
go: downloading github.com/coreos/go-semver v0.3.1
go: downloading golang.org/x/exp v0.0.0-20220722155223-a9213eeb770e
go: downloading github.com/matttproud/golang_protobuf_extensions v1.0.4
go: downloading github.com/cert-manager/cert-manager v1.20.1
go: github.com/syseleven/designate-certmanager-webhook tested by
	github.com/syseleven/designate-certmanager-webhook.test imports
	github.com/cert-manager/cert-manager/test/acme/dns: cannot find module providing package github.com/cert-manager/cert-manager/test/acme/dns