deps: update dependency cert-manager/cert-manager to v1.11.0 #627
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.10.1
->v1.11.0
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
cert-manager/cert-manager
v1.11.0
Compare Source
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:
Thanks also to the following cert-manager maintainers for their contributions during this release:
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
--max-concurrent-challenges
controller flag to the helm chart (#5638, @lvyanru8200)ko
and redeploying cert-manager to the cluster referenced by your current KUBECONFIG context. (#5655, @wallrj)LiteralSubject
field, all mandatory OIDs are now supported for LDAP certificates (rfc4514). (#5587, @SpectralHiss)ExperimentalGatewayAPISupport
alpha feature must ensure thatv1beta
of Gateway API is installed in cluster. (#5583, @lvyanru8200)Bug or Regression
vcert
was upgraded tov4.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 withWebSDK CertRequest Module Requested Certificate
orThis 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 ofalgorithm: Ed25519
in Certificate resources with VaaS. (#5674, @maelvls)golang/x/net
to fix CVE-2022-41717 (#5632, @SgtCoDFish)golang.org/x/text
vulnerability (#5562, @SgtCoDFish)extraArgs
in Helm takes precedence over the new acmesolver image options (#5702, @SgtCoDFish)Other
certificate.spec.secretName
Secrets will now be labelled with thecontroller.cert-manager.io/fao
label (#5703, @irbekrm)v1.10.2
Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
v1.10.2 is primarily a performance enhancement release which might reduce memory consumption by up to 50% in some cases thanks to some brilliant work by @irbekrm! 🎉
It also patches several vulnerabilities reported by scanners and updates the base images used for cert-manager containers. In addition, it removes a potentially confusing log line which had been introduced in v1.10.0 which implied that an error had occurred when using external issuers even though there'd been no error.
Changes since
v1.10.1
Feature
Bug or Regression
golang.org/x/text
vulnerability (#5592, @SgtCoDfish)Other (Cleanup or Flake)
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.