Update Helm release cert-manager to v1.21.1 (main)
This MR contains the following updates:
| Package | Update | Change |
|---|---|---|
| cert-manager (source) | patch | v1.21.0 -> v1.21.1 |
⚠️ WarningSome dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
cert-manager/cert-manager (cert-manager)
v1.21.1
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
v1.21.1 fixes a controller panic for Certificates with spec.renewal.policy: Disabled, a regression in 1.21.0 which caused log spam and dropped Secret informer events, Issuers and ClusterIssuers getting stuck at Ready=False (InvalidSolver) when a referenced ACME DNS-01 solver Secret is created after the Issuer, and the commented Gateway API example in the Helm chart values. It also updates several dependencies to fix reported security vulnerabilities.
All users should upgrade.
Changes by Kind
Bug or Regression
- Avoid controller panic if a Certificate sets spec.renewal.policy=Disabled (#9038, @sklirg)
- Fix Issuer/ClusterIssuer stuck at Ready=False/InvalidSolver after a missing ACME DNS-01 solver Secret is created (#9083, @SebTardif)
- Fix log spam and dropped Secret informer events for non-cert-manager Secrets, caused by a generics regression introduced in 1.21.0. (#9037, @wallrj-cyberark)
- Fixed the commented Gateway API config example in the Helm chart values to use
gatewayAPI.enabledinstead of the invalidgatewayAPI.enable. (#9012, @mateenali66)
Other (Cleanup or Flake)
- Bump
golang.org/x/textto v0.40.0 to fix a reported security vulnerability (#9039, @wallrj-cyberark) - Bump
google.golang.org/grpcto v1.82.1 to fix a reported security vulnerability (#9063) - Bump
github.com/google/cel-goto v0.29.0 to fix a reported security vulnerability (#9072) - Bump
go.opentelemetry.io/otelto v1.44.0 to fix a reported security vulnerability (#9073) - Update distroless base images (#9000, #9025)
Configuration
- If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot Sylva instance.
CI configuration couldn't be handle by MR description. A dedicated comment has been posted to control it.
If no checkbox is checked, a default pipeline will be enabled (capm3, or capo if capo label is set)