Update Helm release cert-manager to v1.10.0 #62
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.9.1->v1.10.0Release Notes
cert-manager/cert-manager
v1.10.0Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
Version 1.10 adds a variety of quality-of-life fixes and features including improvements to the test suite.
Changes since v1.9.1
Feature
issuer_name,issuer_kindandissuer_grouplabels tocertificate_expiration_timestamp_seconds,certmanager_certificate_renewal_timestamp_secondsandcertmanager_certificate_ready_statusmetrics (#5461, @dkulchinsky)cert-manager.io/private-key-secret-name. This resolves an issue whereby a request would never be signed when the target Secret was not created or was misconfigured before the request. (#5336, @JoshVanL)experimental.cert-manager.io/private-key-secret-name. This resolves an issue whereby a request would never be signed when the target Secret was not created or was misconfigured before the request.CertificateSigningRequets will also now no-longer be marked as failed when the target private key Secret is malformed- now only firing an event. When the Secret data is resolved, the request will attempt issuance. (#5379, @JoshVanL)
commonLabelswhich gives you the capability to add the same label on all the resource deployed by the chart. (#5208, @thib-mary)Bug or Regression
experimental.cert-manager.io/private-key-secret-namedoesn't exist. (#5323, @JoshVanL)accessKeyIDorsecretAccessKeyID. (#5339, @JoshVanL)cmctlandkubectl cert-managernow report their actual versions instead of "canary", fixing issue #5020 (#5022, @maelvls)Other
1.19(#5466, @lucacome).bazeland.bzlfiles from cert-manager now that bazel has been fully replaced (#5340, @SgtCoDFish)v0.25.2. (#5456, @lucacome)BREAKING: this change will break scripts/ CI that depend on
cert-managerbeing the container name. (#5410, @rgl)Thank You!
Thank you to the following community members who had a merged PR for this version - your contributions are at the heart of everything we do!
Thanks also to the following maintainers who worked on cert-manager 1.10:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.