chore(deps): update helm chart cert-manager to v1.5.0 #598
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.4.2
->v1.5.0
Release Notes
jetstack/cert-manager
v1.5.0
Compare Source
Release notes for release-1.5
cert-manager 1.5 is the first release to support Kubernetes 1.22.
Note: in cert-manager 1.7, the API versions
v1alpha2
,v1alpha3
andv1beta1
will be removed in cert-manager 1.7. Keep in mind that you will have to change all your YAML manifests that use a deprecated API version to usecert-manager.io/v1
instead, and re-apply them before cert-manager 1.7.Changelog since 1.4
Changes by Kind
Feature
creation of ACME certificates for the sig-network Gateway API Gateway, when annotated
similarly to existing support for Ingresses. (#4158, @maelvls)
ctl experimental create certificatesigningrequest
for creating a Kuberenetes CertificateSigningRequest based upon a cert-manager Certificate manifest file (#4106, @JoshVanL)Ed25519
private keys and signatures for Certificates (#4079, @annerajb)the CertificateSigningRequests support is experimental and requires the use of a flag on the
controller:
--feature-gates=ExperimentalCertificateSigningRequestControllers=true
(#4112, @JoshVanL)the CertificateSigningRequests support is experimental and requires the use of a flag on the
controller:
--feature-gates=ExperimentalCertificateSigningRequestControllers=true
(#4100, @JoshVanL)the CertificateSigningRequests support is experimental and requires the use of a flag on the
controller:
--feature-gates=ExperimentalCertificateSigningRequestControllers=true
(#4103, @JoshVanL)the CertificateSigningRequests support is experimental and requires the use of a flag on the
controller:
--feature-gates=ExperimentalCertificateSigningRequestControllers=true
(#4108, @JoshVanL)kubectl cert-manager x install
command is added (#4138, @inteon)Bug or Regression
with a nil pointer exception when using the annotation "cert-manager.io/issuer" on a Gateway that
had an empty
tls
block or withcertificateRef
left empty. (#4293, @maelvls)with a large number of certificates. (#4231, @maelvls)
Other (Cleanup or Flake)
kubectl.kubernetes.io/
,fluxcd.io
,argocd.argoproj.io
are now excluded by default. (#4251, @irbekrm)experimental.cert-manager.io/ca
annotation set. (#4143, @JoshVanL)v1.4.3
Compare Source
Release notes for v1.4.3
Changelog since v1.4.2
Changes by Kind
Bug or Regression
Other (Cleanup or Flake)
Configuration
📅 Schedule: 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 Renovate Bot.