chore(deps): update helm release cert-manager to v1.16.1
-
Review changes -
-
Download -
Patches
-
Plain diff
This MR contains the following updates:
| Package | Update | Change |
|---|---|---|
| cert-manager (source) | minor |
v1.14.5 -> v1.16.1
|
⚠ WarningSome dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
cert-manager/cert-manager (cert-manager)
v1.16.1
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
The cert-manager 1.16 release includes: new Helm chart features, more Prometheus metrics, memory optimizations, and various improvements and bug fixes for the ACME issuer and Venafi Issuer.
📜 Changes since v1.16.0
Bug or Regression
- BUGFIX: Helm schema validation: the new schema validation was too strict for the "global" section. Since the global section is shared across all charts and sub-charts, we must also allow unknown fields. (#7348,
@inteon) - BUGFIX: Helm will now accept percentages for the
podDisruptionBudget.minAvailableandpodDisruptionBudget.maxAvailablevalues. (#7345,@inteon) - Helm: allow
enabledto be set as a value to toggle cert-manager as a dependency. (#7356,@inteon) - BUGFIX: A change in
v1.16.0caused cert-manager's ACME ClusterIssuer to look in the wrong namespace for resources required for the issuance (e.g. credential Secrets). This is now fixed inv1.16.1. (#7342,@inteon)
v1.16.0
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
The cert-manager 1.16 release includes: new Helm chart features, more Prometheus metrics, memory optimizations, and various improvements and bug fixes for the ACME issuer and Venafi Issuer.
⚠ ️ Known issues
- Helm Chart: JSON schema prevents the chart being used as a sub-chart on Rancher RKE.
- ACME DNS01 ClusterIssuer fail while loading credentials from Secret resources.
❗ Breaking changes
- Helm schema validation may reject your existing Helm values files if they contain typos or unrecognized fields.
- Venafi Issuer may fail to renew certificates if the requested duration conflicts with the CA’s minimum or maximum policy settings in Venafi.
- Venafi Issuer may fail to renew Certificates if the issuer has been configured for TPP with username-password authentication.
📜 Changes since v1.15.0
Feature
- Add
SecretRefsupport for Venafi TPP issuer CA Bundle (#7036,@sankalp-at-gh) - Add
renewBeforePercentagealternative torenewBefore(#6987,@cbroglie) - Add a metrics server to the cainjector (#7194,
@wallrj) - Add a metrics server to the webhook (#7182,
@wallrj) - Add client certificate auth method for Vault issuer (#4330,
@joshmue) - Add process and go runtime metrics for controller (#6966,
@mindw) - Added
app.kubernetes.io/managed-by: cert-managerlabel to the cert-manager-webhook-ca Secret (#7154,@jrcichra) - Allow the user to specify a Pod template when using GatewayAPI HTTP01 solver, this mirrors the behavior when using the Ingress HTTP01 solver. (#7211,
@ThatsMrTalbot) - Create token request RBAC for the cert-manager ServiceAccount by default (#7213,
@Jasper-Ben) - Feature: Append cert-manager user-agent string to all AWS API requests, including IMDS and STS requests. (#7295,
@wallrj) - Feature: Log AWS SDK warnings and API requests at cert-manager debug level to help debug AWS Route53 problems in the field. (#7292,
@wallrj) - Feature: The Route53 DNS solver of the ACME Issuer will now use regional STS endpoints computed from the region that is supplied in the Issuer spec or in the
AWS_REGIONenvironment variable. Feature: The Route53 DNS solver of the ACME Issuer now uses the "ambient" region (AWS_REGIONorAWS_DEFAULT_REGION) ifissuer.spec.acme.solvers.dns01.route53.regionis empty; regardless of the flags--issuer-ambient-credentialsand--cluster-issuer-ambient-credentials. (#7299,@wallrj) - Helm: adds JSON schema validation for the Helm values. (#7069,
@inteon) - If the
--controllersflag only specifies disabled controllers, the default controllers are now enabled implicitly. AddeddisableAutoApprovalandapproveSignerNamesHelm chart options. (#7049,@inteon) - Make it easier to configure cert-manager using Helm by defaulting
config.apiVersionandconfig.kindwithin the Helm chart. (#7126,@ThatsMrTalbot) - Now passes down specified duration to Venafi client instead of using the CA default only. (#7104,
@Guitarkalle) - Reduce the memory usage of
cainjector, by only caching the metadata of Secret resources. Reduce the load on the K8S API server whencainjectorstarts up, by only listing the metadata of Secret resources. (#7161,@wallrj) - The Route53 DNS01 solver of the ACME Issuer can now detect the AWS region from the
AWS_REGIONandAWS_DEFAULT_REGIONenvironment variables, which is set by the IAM for Service Accounts (IRSA) webhook and by the Pod Identity webhook. Theissuer.spec.acme.solvers.dns01.route53.regionfield is now optional. The API documentation of theregionfield has been updated to explain when and how the region value is used. (#7287,@wallrj) - Venafi TPP issuer can now be used with a username & password combination with OAuth. Fixes #4653.
Breaking: cert-manager will no longer use the API Key authentication method which was deprecated in 20.2 and since removed in 24.1 of TPP. (#7084,
@hawksight) - You can now configure the pod security context of HTTP-01 solver pods. (#5373,
@aidy) - Helm: New value
webhook.extraEnv, allows you to set custom environment variables in the webhook Pod. Helm: New valuecainjector.extraEnv, allows you to set custom environment variables in the cainjector Pod. Helm: New valuestartupapicheck.extraEnv, allows you to set custom environment variables in the startupapicheck Pod. (#7319,@wallrj)
Bug or Regression
- Adds support (behind a flag) to use a domain qualified finalizer. If the feature is enabled (which is not by default), it should prevent Kubernetes from reporting:
metadata.finalizers: "finalizer.acme.cert-manager.io": prefer a domain-qualified finalizer name to avoid accidental conflicts with other finalizer writers(#7273,@jsoref) - BUGFIX Route53: explicitly set the
aws-globalSTS region which is now required by thegithub.com/aws/aws-sdk-go-v2library. (#7108,@inteon) - BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#7105,
@inteon) - BUGFIX: the dynamic certificate source used by the webhook TLS server failed to detect a root CA approaching expiration, due to a calculation error. This will cause the webhook TLS server to fail renewing its CA certificate. Please upgrade before the expiration of this CA certificate is reached. (#7230,
@inteon) - Bugfix: Prevent aggressive Route53 retries caused by IRSA authentication failures by removing the Amazon Request ID from errors wrapped by the default credential cache. (#7291,
@wallrj) - Bugfix: Prevent aggressive Route53 retries caused by STS authentication failures by removing the Amazon Request ID from STS errors. (#7259,
@wallrj) - Bump
grpc-goto fixGHSA-xr7q-jx4m-x55m(#7164,@SgtCoDFish) - Bump the
go-retryablehttpdependency to fixCVE-2024-6104(#7125,@SgtCoDFish) - Fix Azure DNS causing panics whenever authentication error happens (#7177,
@eplightning) - Fix incorrect indentation of
endpointAdditionalPropertiesin thePodMonitortemplate of the Helm chart (#7190,@wallrj) - Fixes ACME HTTP01 challenge behavior when using Gateway API to prevent unbounded creation of HTTPRoute resources (#7178,
@miguelvr) - Handle errors arising from challenges missing from the ACME server (#7202,
@bdols) - Helm BUGFIX: the cainjector ConfigMap was not mounted in the cainjector deployment. (#7052,
@inteon) - Improve the startupapicheck: validate that the validating and mutating webhooks are doing their job. (#7057,
@inteon) - The
KeyUsagesX.509 extension is no longer added when there are no key usages set (in accordance to RFC 5280 Section 4.2.1.3) (#7250,@inteon) - Update
github.com/Azure/azure-sdk-for-go/sdk/azidentityto addressCVE-2024-35255(#7087,@dependabot[bot])
Other (Cleanup or Flake)
- Old API versions were removed from the codebase.
Removed:
(acme.)cert-manager.io/v1alpha2
(acme.)cert-manager.io/v1alpha3
(acme.)cert-manager.io/v1beta1 (#7278,
@inteon) - Upgrading to client-go
v0.31.0removes a lot of noisyreflector.go: unable to sync list result: internal error: cannot cast object DeletedFinalStateUnknownerrors from logs. (#7237,@inteon) - Bump Go to
v1.23.2(#7324,@cert-manager-bot)
v1.15.3
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
📜 Changes since v1.15.2
Bug or Regression
- BUGFIX: the dynamic certificate source used by the webhook TLS server failed to detect a root CA approaching expiration, due to a calculation error. This will cause the webhook TLS server to fail renewing its CA certificate. Please upgrade before the expiration of this CA certificate is reached. (#7232, @cert-manager-bot)
v1.15.2
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
📜 Changes since v1.15.1
Bug or Regression
- BUGFIX
route53: explicitly set theaws-globalSTS region which is now required by thegithub.com/aws/aws-sdk-go-v2library. (#7189,@cert-manager-bot) - Bump
grpc-goto fixGHSA-xr7q-jx4m-x55m(#7167,@SgtCoDFish) - Fix Azure DNS causing panics whenever authentication error happens (#7188,
@cert-manager-bot) - Fix incorrect value and indentation of
endpointAdditionalPropertiesin thePodMonitortemplate of the Helm chart (#7191,@inteon) - Fixes ACME HTTP01 challenge behavior when using Gateway API to prevent unbounded creation of
HTTPRouteresources (#7186,@cert-manager-bot) - Upgrade
golangfrom1.22.3to1.22.5(#7165,@github-actions)
v1.15.1
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
📜 Changes since v1.15.0
Bug or Regression
- BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#7111, @inteon)
Other (Cleanup or Flake)
- Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to address CVE-2024-35255 (#7092, @ThatsMrTalbot)
- Bump the go-retryablehttp dependency to fix CVE-2024-6104 (#7130, @SgtCoDFish)
v1.15.0
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
cert-manager 1.15 promotes several features to beta, including GatewayAPI support (ExperimentalGatewayAPISupport), the ability to provide a subject in the Certificate that will be used literally in the CertificateSigningRequest (LiteralCertificateSubject) and the outputting of additional certificate formats (AdditionalCertificateOutputFormats).
[!NOTE]
The
cmctlbinary have been moved to https://github.com/cert-manager/cmctl/releases. For the startupapicheck Job you should update references to point atquay.io/jetstack/cert-manager-startupapicheck
[!NOTE]
From this release, the Helm chart will no longer uninstall the CRDs when the chart is uninstalled. If you want the CRDs to be removed on uninstall use
crds.keep=falsewhen installing the Helm chart.
Community
Thanks again to all open-source contributors with commits in this release, including: @Pionerd, @SgtCoDFish, @ThatsMrTalbot, @andrey-dubnik, @bwaldrep, @eplightning, @erikgb, @findnature, @gplessis, @import-shiburin, @inteon, @jkroepke, @lunarwhite, @mangeshhambarde, @pwhitehead-splunk & @rodrigorfk, @wallrj.
Thanks also to the following cert-manager maintainers for their contributions during this release: @SgtCoDFish, @SpectralHiss, @ThatsMrTalbot, @hawksight, @inteon, @maelvls & @wallrj.
Equally thanks to everyone who provided feedback, helped users and raised issues on GitHub and Slack and joined our meetings!
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 Venafi for contributing developer time and resources towards the continued maintenance of cert-manager projects.
Changes by Kind
Feature
- GatewayAPI support has graduated to Beta. Add the
--enable-gateway-apiflag to enable the integration. (#6961, @ThatsMrTalbot) - Add support to specify a custom key alias in a JKS Keystore (#6807, @bwaldrep)
- Add the ability to communicate with Vault via mTLS when strict client certificates is enabled at Vault server side (#6614, @rodrigorfk)
- Added option to provide additional audiences in the service account auth section for vault (#6718, @andrey-dubnik)
- Venafi Issuer now sends a cert-manager HTTP User-Agent header in all Venafi Rest API requests.
For example:
cert-manager-certificaterequests-issuer-venafi/v1.15.0+(linux/amd64)+cert-manager/ef068a59008f6ed919b98a7177921ddc9e297200. (#6865, @wallrj) - Add hint to validation error message to help users of external issuers more easily fix the issue if they specify a Kind but forget the Group (#6913, @SgtCoDFish)
- Add support for numeric OID types in LiteralSubject. Eg. "1.2.3.4=String Value" (#6775, @inteon)
- Promote the
LiteralCertificateSubjectfeature to Beta. (#7030, @inteon) - Promoted the AdditionalCertificateOutputFormats feature gate to Beta (enabled by default). (#6970, @erikgb)
- The Helm chart now allows you to supply
extraObjects; a list of yaml manifests which will helm will install and uninstall with the cert-manager manifests. (#6424, @gplessis) - Update the Route53 provider to support fetching credentials using AssumeRoleWithWebIdentity (#6878, @pwhitehead-splunk)
- Helm can now add optional hostAliases to cert-manager Pod to allow the DNS self-check to pass in custom scenarios. (#6456, @Pionerd)
- Added a new Ingress annotation for copying specific Ingress annotations to Certificate's secretTemplate (#6839, @mangeshhambarde)
- Added option to define additional token audiences for the Vault Kubernetes auth (#6744, @andrey-dubnik)
- Allow
cert-manager.io/allow-direct-injectionin annotations (#6801, @jkroepke)
Design
- Remove repetitive words (#6949, @findnature)
Bug or Regression
- BUGFIX: Fixes issue with JSON-logging, where only a subset of the log messages were output as JSON. (#6779, @inteon)
- BUGFIX: JKS and PKCS12 stores now contain the full set of CAs specified by an issuer (#6806, @bwaldrep)
- BUGFIX: cainjector leaderelection flag/config option defaults are missing (#6816, @inteon)
- BUGFIX: cert-manager issuers incorrectly copied the critical flag from the CSR instead of re-calculating that field themselves. (#6724, @inteon)
- Breaking Change: Fixed unintended certificate chain is used if
preferredChainis configured. (#6755, @import-shiburin) - Bugfix: LiteralSubjects with a #= value can result in memory issues due to faulty BER parser (github.com/go-asn1-ber/asn1-ber). (#6770, @inteon)
- DigitalOcean: Ensure that only TXT records are considered for deletion when cleaning up after an ACME challenge (#6875, @SgtCoDFish)
- Fix backwards incompatible removal of default prometheus Service resource. (#6699, @inteon)
- Fix broken cainjector image value in Helm chart (#6692, @SgtCoDFish)
- Helm: Fix a bug in the logic that differentiates between 0 and an empty value. (#6713, @inteon)
- Make sure the Azure SDK error messages are stable. (#6676, @inteon)
- When using the literalSubject on a Certificate, the webhook validation for the common name now also points to the literalSubject. (#6767, @lunarwhite)
- Bump golang.org/x/net to fix CVE-2023-45288 (#6929, @SgtCoDFish)
- Fix ACME issuer being stuck waiting for DNS propagation when using Azure DNS with multiple instances issuing for the same FQDN (#6351, @eplightning)
- Fix cainjector ConfigMap not mounted in the cainjector deployment. (#7055, @inteon)
- Added
disableAutoApprovalandapproveSignerNamesHelm chart options. (#7054, @inteon)
Other (Cleanup or Flake)
-
⚠ ️ Possibly breaking: Helm will now keep the CRDs when you uninstall cert-manager by default to prevent accidental data loss. (#6760, @inteon) - New
crds.keepandcrds.enabledHelm options can now be used instead of theinstallCRDsoption. (#6760, @inteon) - Bump base images (#6840, @inteon)
- Bump github.com/go-jose/go-jose to v3.0.3 to fix CVE-2024-28180 (#6854, @wallrj)
- Removed deprecated util functions that have been replaced by the
slicesandk8s.io/apimachinery/pkg/utilpackages. Removed deprecated CSR functions which have been replaced with other functions in thepkg/util/pkipackage. (#6730, @inteon) - Upgrade go to 1.21.8: fixes CVE-2024-24783 (#6823, @inteon)
- Upgrade go to latest version 1.22.1 (#6831, @inteon)
- Upgrade google.golang.org/protobuf: fixing GO-2024-2611 (#6827, @inteon)
-
cmctlandkubectl cert-mangerhave been moved to the https://github.com/cert-manager/cmctl repo and will be versioned separately starting with cmctl v2.0.0 (#6663, @inteon) - Graduate the 'DisallowInsecureCSRUsageDefinition' feature gate to GA. (part 2) (#6963, @inteon)
- Remove deprecated
pkg/util/pki/ParseSubjectStringToRawDERBytesfunction. (#6994, @inteon) - Upgrade Kind to v0.23.0 and update supported node image digests (#7020, @github-actions[bot])
- If the
--controllersflag only specifies disabled controllers, the default controllers are now enabled implicitly. (#7054, @inteon) - Upgrade to Go 1.22.3, fixing
GO-2024-2824. (#6996, @github-actions[bot])
v1.14.7
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
📜 Changes since v1.14.6
Bugfixes
- BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#7113, @cert-manager-bot)
Other (Cleanup or Flake)
- Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to address CVE-2024-35255 (#7093, @ThatsMrTalbot)
v1.14.6
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
📜 Changes since v1.14.5
Other (Cleanup or Flake)
- Upgrade Go to 1.21.10, fixing GO-2024-2824 (https://github.com/advisories/GHSA-2jwv-jmq4-4j3r). (#7008, @inteon)
- Helm: the cainjector ConfigMap was not mounted in the cainjector deployment. (#7053, @cert-manager-bot)
- Updated Go to 1.21.11 bringing in security fixes for archive/zip and net/netip. (#7076, @ThatsMrTalbot)
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.