cert-manager - v1.11.0

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

v1.11.0 includes a drastic reduction in cert-manager's runtime memory usage, a slew of improvements to AKS integrations and various other tweaks, fixes and improvements, all towards cert-manager's goal of being the best way to handle certificates in modern Cloud Native applications.

Community

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

• @cmcga1125
• @karlschriek
• @lvyanru8200
• @mmontes11
• @pinkfloydx33
• @sathyanarays
• @weisdd
• @yann-soubeyrand
• @joycebrum
• @Git-Jiro
• @thib-mary
• @yk
• @RomanenkoDenys
• @lucacome
• @yanggangtony

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

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

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 since cert-manager v1.10

For an overview of new features, see the v1.11 release notes!

Feature

• Helm: allow configuring the image used by ACME HTTP-01 solver (#5554, @yann-soubeyrand)
• Add the --max-concurrent-challenges controller flag to the helm chart (#5638, @lvyanru8200)
• Adds the ability to specify a custom CA bundle in Issuers when connecting to an ACME server (#5644, @SgtCoDFish)
• Enable testing against Kubernetes 1.26 and test with Kubernetes 1.26 by default (#5646, @SgtCoDFish)
• Experimental make targets for pushing images to an OCI registry using ko and redeploying cert-manager to the cluster referenced by your current KUBECONFIG context. (#5655, @wallrj)
• Add ability to run acmesolver pods as root if desired. The default is still to run as non-root. (#5546, @cmcga1125)
• Add support for DC and UID in LiteralSubject field, all mandatory OIDs are now supported for LDAP certificates (rfc4514). (#5587, @SpectralHiss)
• Add support for Workload Identity to AzureDNS resolver (#5570, @weisdd)
• Breaking: updates the gateway API integration to use the more stable v1beta1 API version. Any users of the cert-manager ExperimentalGatewayAPISupport alpha feature must ensure that v1beta of Gateway API is installed in cluster. (#5583, @lvyanru8200)
• Certificate secrets get refreshed if the keystore format change (#5597, @sathyanarays)
• Introducing UseCertificateRequestBasicConstraints feature flag to enable Basic Constraints in the Certificate Signing Request (#5552, @sathyanarays)
• Return error when Gateway has a cross-namespace secret ref (#5613, @mmontes11)
• Signers fire an event on CertificateRequests which have not been approved yet. Used for informational purposes so users understand why a request is not progressing. (#5535, @JoshVanL)

Bug or Regression

• Don't log errors relating to self-signed issuer checks for external issuers (#5681, @SgtCoDFish)
• Fixed a bug in AzureDNS resolver that led to early reconciliations in misconfigured Workload Identity-enabled setups (when Federated Identity Credential is not linked with a controller's k8s service account) (#5663, @weisdd)
• Use manually specified temporary directory template when verifying CRDs (#5680, @SgtCoDFish)
• vcert was upgraded to v4.23.0, fixing two bugs in cert-manager. The first bug was preventing the Venafi issuer from renewing certificates when using TPP has been fixed. You should no longer see your certificates getting 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.. The second bug that was fixed prevented the use of algorithm: Ed25519 in Certificate resources with VaaS. (#5674, @maelvls)
• Upgrade golang/x/net to fix CVE-2022-41717 (#5632, @SgtCoDFish)
• Bug fix: When using feature gates with the helm chart, enable feature gate flags on webhook as well as controller (#5584, @lvyanru8200)
• Fix golang.org/x/text vulnerability (#5562, @SgtCoDFish)
• Fixes a bug that caused the Vault issuer to omit the Vault namespace in requests to the Vault API. (#5591, @wallrj)
• The Venafi Issuer now supports TLS 1.2 renegotiation, so that it can connect to TPP servers where the vedauth API endpoints are configured to accept client certificates. (Note: This does not mean that the Venafi Issuer supports client certificate authentication). (#5568, @wallrj)
• Upgrade to go 1.19.4 to fix CVE-2022-41717 (#5619, @SgtCoDFish)
• Upgrade to latest go minor release (#5559, @SgtCoDFish)
• Ensure extraArgs in Helm takes precedence over the new acmesolver image options (#5702, @SgtCoDFish)
• Fix cainjector's --namespace flag. Users who want to prevent cainjector from reading all Secrets and Certificates in all namespaces (i.e to prevent excessive memory consumption) can now scope it to a single namespace using the --namespace flag. A cainjector that is only used as part of cert-manager installation only needs access to the cert-manager installation namespace. (#5694, @irbekrm)
• Fixes a bug where cert-manager controller was caching all Secrets twice (#5691, @irbekrm)

Other

• certificate.spec.secretName Secrets will now be labelled with the controller.cert-manager.io/fao label (#5703, @irbekrm)
• Upgrade to go 1.19.5 (#5714, @yanggangtony)