v1.12.0-beta.1

v1.12.0-beta.1

⚠️ cert-manager v1.12.0-beta.0 is a pre-release beta version intended for testing. It might not be suitable for production uses.

Changelog since v1.12.0-beta.0

Changes by Kind

Feature

• Added support for json logging (using --logging-format=json) (#5828, @malovme)
• 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)
• Webhook now logs requests to mutating/validating webhook (with --v=5 flag) (#5975, @tobotg)

Design

• ServerSideApply: The feature gate ServerSideApply=true configures the ca-injector controller to use Kubernetes Server Side Apply on CA Injector injectable target resources. (#5991, @inteon)

Documentation

• Fixes broken reference links in Helm chart values.yaml (#5999, @SgtCoDFish)

Bug or Regression

• Adds missing comparisons for certain fields which were incorrectly skipped if a LiteralSubject was set (#5747, @inteon)
• Check JKS/PKCS12 truststore in Secrets only if issuer provides the CA (#5972, @vinzent)

Other (Cleanup or Flake)

• Caches metadata only for filtered Pods and Services (#5976, @irbekrm)
• Storing the latest private key hash on issuer status prevents unnecessary calls to ACME server during controller startup (#6006, @vidarno)
• Tests on Kubernetes v1.27.1 by default. (#5979, @irbekrm)
• Updates Kubernetes libraries to v0.27.1. (#5961, @lucacome)

Uncategorized

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