NEW: Get project updates onTwitterandMastodon

Release 1.19

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

This release focuses on expanding platform compatibility, improving deployment flexibility, enhancing observability, and addressing key reliability issues. Users should review breaking changes and new features before upgrading.

Be sure to review all new features and changes below, and read the full release notes carefully before upgrading.

Major Themes

  • Expanded Platform Compatibility

    • IPv6 rules have been added to the default network policy, improving support for dual-stack clusters and modern infrastructure.

  • Deployment Flexibility

    • The Helm chart now supports a global nodeSelector, allowing users to easily target specific nodes for all cert-manager components.

  • ACME and Certificate Management Enhancements

    • New feature gates for ACME HTTP01 challenge solvers, support for the ACME profiles extension, and more granular resource management for solver pods.
    • API defaults for issuer references and improved type safe server-side apply requests.

  • Observability and Metrics

    • Introduction of new Prometheus metrics and updates to existing metrics for better monitoring.
    • The controller, webhook, and ca-injector now log their version and git commit on startup for improved debugging.

  • Reliability and Bug Fixes

    • Increased ACME challenge authorization timeout, improved validation for ingress configurations, and support for larger PEM certificates.
    • Numerous bug fixes and improvements to error messages.

  • General Cleanup and Upgrades

    • Major upgrade of Akamai SDK, improved Helm resource naming, and updated test infrastructure to use the latest Kubernetes node images.

Community

As always, we'd like to thank all of the community members who helped in this release cycle, including all below who merged a PR and anyone that helped by commenting on issues, testing, or getting involved in cert-manager meetings. We're lucky to have you involved.

A special thanks to:

for their contributions, comments and support!

Also, thanks to the cert-manager maintainer team for their help in this release:

And finally, thanks to the cert-manager steering committee for their feedback in this release cycle:

v1.19.0

Changes since v1.18.2:

Feature

  • Add IPv6 rules to the default network policy (#7726, @jcpunk)
  • Add global.nodeSelector to helm chart to allow for a single nodeSelector to be set across all services. (#7818, @StingRayZA)
  • Add generated applyconfigurations allowing clients to make type safe server-side apply requests for cert-manager resources. (#7866, @erikgb)
  • Added API defaults to issuer references group (cert-manager.io) and kind (Issuer). (#7414, @erikgb)
  • Added certmanager_certificate_challenge_status Prometheus metric. (#7736, @hjoshi123)
  • Added protocol field for rfc2136 DNS01 provider (#7881, @hjoshi123)
  • CAInjectorMerging has been promoted to BETA and is now enabled by default (#8017, @ThatsMrTalbot)
  • Feature: Add support for ACME profiles extension. (#7777, @wallrj)
  • Support configurable resource requests and limits for ACME HTTP01 solver pods through ClusterIssuer and Issuer specifications, allowing granular resource management that overrides global --acme-http01-solver-resource-* settings. (#7972, @lunarwhite)
  • The controller, webhook and ca-injector now logs its version and git commit on startup for easier debugging and support. (#8072, @prasad89)
  • Updated certificate metrics to the collector approach. (#7856, @hjoshi123)

Bug or Regression

  • ACME: Increased challenge authorization timeout to 2 minutes to fix error waiting for authorization (#7796, @hjoshi123)
  • BUGFIX: permitted URI domains were incorrectly used to set the excluded URI domains in the CSR's name constraints (#7816, @kinolaev)
  • Enforced ACME HTTP-01 solver validation to properly reject configurations when multiple ingress options (class, ingressClassName, name) are specified simultaneously (#8021, @lunarwhite)
  • Increase maximum sizes of PEM certificates and chains which can be parsed in cert-manager, to handle leaf certificates with large numbers of DNS names or other identities (#7961, @SgtCoDFish)
  • Reverted adding the global.rbac.disableHTTPChallengesRole Helm option. (#7836, @inteon)
  • Use the latest version of ingress-nginx in E2E tests to ensure compatibility (#7792, @wallrj)

Other (Cleanup or Flake)

  • Helm: Fix naming template of tokenrequest RoleBinding resource to improve consistency (#7761, @lunarwhite)
  • Improve error messages when certificates, CRLs or private keys fail admission due to malformed or missing PEM data (#7928, @SgtCoDFish)
  • Major upgrade of Akamai SDK. NOTE: The new version has not been fully tested end-to-end due to the lack of cloud infrastructure. (#8003, @hjoshi123)
  • Update kind images to include the Kubernetes 1.33 node image (#7786, @wallrj)
  • Use maps.Copy for cleaner map handling (#8092, @quantpoet)