This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
chore(deps): update cert-manager to v1.12.2 (minor) #196
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}
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
d4ee069
to
91ef592
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
91ef592
to
d5ec21e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
d5ec21e
to
e6c787e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
e6c787e
to
01e232a
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
01e232a
to
2bc0909
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
2bc0909
to
aebc908
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
2 times, most recently
from
286c816
to
9ecd3b1
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
9ecd3b1
to
27daf01
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
27daf01
to
f743f34
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
f743f34
to
42910fd
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
42910fd
to
e9c1d82
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
e9c1d82
to
8b183dd
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
8b183dd
to
fdfb05e
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
fdfb05e
to
60a0bdf
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
60a0bdf
to
dce632b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
dce632b
to
ca9ab60
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
ca9ab60
to
577050b
Compare
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
577050b
to
5ff123d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cert-manager
branch
from
5ff123d
to
0c6148a
Compare
renovate
bot
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.4->v1.12.2v1.4.4->v1.12.2v1.4.4->v1.12.2v1.4.4->v1.12.2⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
jetstack/cert-manager
v1.12.2Compare Source
Changes by Kind
Uncategorized
cmctl check api --wait 0exited without output; we now make sure we perform the API check at least once (#6116, @jetstack-bot)v1.12.1Compare Source
v1.12.1
This release contains a couple dependency bumps and changes to ACME external webhook library.
Known issues
cmctlAPI check is broken in v1.12.1. We suggest that you do not upgradecmctlto this version. The fix will be released in v1.12.2.See #6116 for context.
Changes by Kind
Other (Cleanup or Flake)
Uncategorized
v0.27.2. (#6077, @lucacome)v0.15.0(#6098, @lucacome)v1.12.0Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
cert-manager v1.12 brings support for JSON logging, a lower memory footprint, support for ephemeral service account tokens with Vault, improved dependency management and support for the ingressClassName field.
The full release notes are available at https://cert-manager.io/docs/release-notes/release-notes-1.12.
Known issues
cmctlAPI check is broken in v1.12.0. We suggest that you do not upgradecmctlto this version. The fix will be released in v1.12.2.See #6116 for context.
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:
Equally thanks to everyone who provided feedback, helped users and raised issues on Github and Slack, joined our meetings and talked to us at Kubecon!
Special thanks to @erikgb for continuously great input and feedback and to @lucacome for always ensuring that our kube deps are up to date!
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 by Kind
Feature
--concurrent-workersflag that lets you control the number of concurrent workers for each of our controllers. (#5936, @inteon)acme.solvers.http01.ingress.podTemplate.spec.imagePullSecretsfield to issuer spec to allow to specify image pull secrets for the ACME HTTP01 solver pod. (#5801, @malovme)--watch-certsflag was renamed to--enable-certificates-data-source. (#5766, @irbekrm)--dns01-recursive-nameservers,--enable-certificate-owner-ref, and--dns01-recursive-nameservers-onlythrough Helm values. (#5614, @jkroepke)ingressClassName. The credit goes to @dsonck92 for implementing the initial PR. (#5849, @maelvls)serviceAccountReffield, cert-manager generates a short-lived token associated to the service account to authenticate to Vault. Along with this new feature, we have added validation logic in the webhook in order to check thevault.authfield when creating an Issuer or ClusterIssuer. Previously, it was possible to create an Issuer or ClusterIssuer with an invalid value forvault.auth. (#5502, @maelvls)/livezendpoint and a default liveness probe, which fails if leader election has been lost and for some reason the process has not exited. The liveness probe is disabled by default. (#5962, @wallrj)--v=5flag) (#5975, @tobotg)Design
This is not necessarily a breaking change as due to a race condition this may already have been the case. (#5887, @irbekrm)
Documentation
values.yamlare now working (#5999, @SgtCoDFish)Bug or Regression
cmctl x install. (#5720, @irbekrm)--acme-http01-solver-imagegiven to the variableacmesolver.extraArgsnow has precedence over the variableacmesolver.image. (#5693, @SgtCoDFish)jksandpkcs12fields on a Certificate resource with a CA issuer that doesn't set theca.crtin the Secret resource, cert-manager no longer loop trying to copyca.crtintotruststore.jksortruststore.p12. (#5972, @vinzent)literalSubjectfield on a Certificate resource, the IPs, URIs, DNS names, and email addresses segments are now properly compared. (#5747, @inteon)Other (Cleanup or Flake)
make go-workspacetarget for generating a go.work file for local development (#5935, @SgtCoDFish)**BREAKING:*- users who are relying on cainjector to work when
certificates.cert-manager.ioCRD is not installed in the cluster, now need to pass--watch-certificates=falseflag to cainjector else it will not start.Users who only use cainjector as cert-manager's internal component and have a large number of
Certificateresources in cluster can pass--watch-certificates=falseto avoid cainjector from cachingCertificateresources and save some memory. (#5746, @irbekrm)automountServiceAccountTokenturned off. (#5754, @wallrj)SecretsFilteredCachingfeature flag. The filtering mechanism might, in some cases, slightly slow down issuance or cause additional requests to kube-apiserver because unlabelled Secret resources that cert-manager controller needs will now be retrieved from kube-apiserver instead of being cached locally. To prevent this from happening, users can label all issuer Secret resources with thecontroller.cert-manager.io/fao: truelabel. (#5824, @irbekrm)POTENTIALLY BREAKING: this PR slightly changes how the name of the Challenge resources are calculated. To avoid duplicate issuances due to the Challenge resource being recreated, ensure that there is no in-progress ACME certificate issuance when you upgrade to this version of cert-manager. (#5901, @irbekrm)
v0.26.2. (#5820, @lucacome)v0.26.3. (#5907, @lucacome)v0.27.1. (#5961, @lucacome)certificate.spec.secretNameis a validSecretname (#5967, @avi-08)certificate.spec.secretNameSecrets will now be labelled withcontroller.cert-manager.io/faolabel (#5660, @irbekrm)Uncategorized
v1.11.4Compare Source
Changes by Kind
Other (Cleanup or Flake)
Dependencies
Changed
v1.11.3Compare Source
v1.11.3 mostly contains ACME library changes. API Priority and Fairness feature is now disabled in the external webhook's extension apiserver.
Changes by Kind
Other (Cleanup or Flake)
v1.11.2Compare Source
Changelog since v1.11.1
Changes by Kind
Bug or Regression
Other (Cleanup or Flake)
Bump the distroless base images (#5930, @maelvls)
Bumps Docker libraries to fix vulnerability scan alert for CVE-2023-28840, CVE-2023-28841, CVE-2023-28842 (#6037, @irbekrm)
Cert-manager was not actually affected by these CVEs which are all to do with Docker daemon's overlay network.
Bumps Kube libraries v0.26.0 -> v0.26.4 (#6038, @irbekrm)
This might help with running cert-manager v1.11 on Kubernetes v1.27, see #6038
v1.11.1Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
In v1.11.1, we updated the base images used for cert-manager containers. In addition, the users of the Venafi issuer will see less certificates repeatedly failing.
If you are a user of Venafi TPP and have been having issues with the error message
This certificate cannot be processed while it is in an error state. Fix any errors, and then click Retry, please use this version.Changes since v1.11.0
Bug or Regression
cmctl x install, to work around a hardcoded Kubernetes version in Helm. (#5726, @SgtCoDFish)Other (Cleanup or Flake)
v1.11.0Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
v1.11.0includes 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.10For an overview of new features, see the v1.11 release notes!
Feature
--max-concurrent-challengescontroller flag to the helm chart (#5638, @lvyanru8200)koand redeploying cert-manager to the cluster referenced by your current KUBECONFIG context. (#5655, @wallrj)LiteralSubjectfield, all mandatory OIDs are now supported for LDAP certificates (rfc4514). (#5587, @SpectralHiss)ExperimentalGatewayAPISupportalpha feature must ensure thatv1betaof Gateway API is installed in cluster. (#5583, @lvyanru8200)Bug or Regression
vcertwas 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 CertificateorThis 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: Ed25519in Certificate resources with VaaS. (#5674, @maelvls)golang/x/netto fix CVE-2022-41717 (#5632, @SgtCoDFish)golang.org/x/textvulnerability (#5562, @SgtCoDFish)extraArgsin Helm takes precedence over the new acmesolver image options (#5702, @SgtCoDFish)Other
certificate.spec.secretNameSecrets will now be labelled with thecontroller.cert-manager.io/faolabel (#5703, @irbekrm)Known issues
If you are importing cert-manager as a library to run conformance tests against your DNS webhook solver implementation, please make sure that you import a version with a fix, https://github.com/cert-manager/cert-manager/issues/5725#issuecomment-13972457575757
v1.10.2Compare 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.1Feature
Bug or Regression
golang.org/x/textvulnerability (#5592, @SgtCoDfish)Other (Cleanup or Flake)
v1.10.1Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
cert-manager v1.10.1 is a bug fix release which fixes a problem which prevented the Venafi Issuer from connecting to TPP servers where the vedauth API endpoints were configured to accept client certificates.
It is also compiled with a newer version of Go 1.19 (v1.19.3) which fixes some vulnerabilities in the Go standard library.
Changes since
v1.10.0Bug or Regression
vedauthAPI endpoints are configured to accept client certificates.(Note: This does not mean that the Venafi Issuer supports client certificate authentication).
(#5576, @wallrj)
(#5560, @SgtCoDFish )
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
Breaking Changes (You MUST read this before you upgrade!)
Container Name Changes
This change is only relevant if you install cert-manager using Helm or the static manifest files.
v1.10.0changes the names of containers in pods created by cert-manager.The names are changed to better reflect what they do; for example, the container in the controller pod had its name changed from
cert-managertocert-manager-controller,and the webhook pod had its container name changed from
cert-managertocert-manager-webhook.This change could cause a break if you:
If both of these are true, you may need to update your automation before you upgrade.
On OpenShift the cert-manager Pods may fail until you modify Security Context Constraints
In cert-manager 1.10 the secure computing (seccomp) profile for all the Pods is set to RuntimeDefault. (See cert-manager#5259.) The securityContext fields of the Pod are set as follows:
On some versions and configurations of OpenShift this can cause the Pod to be rejected by the Security Context Constraints admission webhook.
Read full release notes to learn if this might affect you and how to fix it.
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)Breaking: this might require changes for OpenShift deployments. Read full release notes to learn more.
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:
v1.9.2Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
cert-manager
v1.9.2is a bug fix release which fixes an issue where CertificateRequests marked as InvalidRequest did not properly trigger issuance failure handling leading to 'stuck' requests, and a problem which prevented the Venafi Issuer from connecting to TPP servers where thevedauthAPI endpoints were configured to accept client certificates.It is also compiled with a newer version of Go 1.18 (
v1.18.8) which fixes some vulnerabilities in the Go standard library.Changes since
v1.9.1Bug or Regression
(#5371, @munnerz )
vedauthAPI endpoints are configured to accept client certificates. (Note: This does not mean that the Venafi Issuer supports client certificate authentication).(#5577, @wallrj)
(#5561, @SgtCoDFish)
v1.9.1Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
Version 1.9.1 is a bugfix release which removes an incorrect check in the Route53 DNS solver. This accidental change prevented the use of credentials derived from instance metadata or AWS pod metadata.
Thanks to @danquack and @ArchiFleKs for raising this issue, and @danquack and @JoshVanL for fixing it!
Changes since v1.9.0
Bug
accessKeyIDorsecretAccessKeyID. (#5341, @JoshVanL @danquack )v1.9.0Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
The new version adds alpha support for using cert-manager
Certificates in scenarios where the ordering of the Relative Distinguished Names (RDN) sequence that constitutes an X.509 certificate's subject needs to be preserved; improves the ability to configure theCertificatecreated via ingress-shim using annotations on theIngressresource; introduces various changes/improvements in contributor flow; and finishes the new make-based contributor workflow.Major Themes
Literal Certificate Subjects
cert-manager's
Certificateallows users to configure the subject fields of the X.509 certificate viaspec.subjectandspec.commonNamefields. The X.509 spec states that the subject is an (ordered) sequence of Relative Distinguished Names (RDN).cert-manager does not strictly abide by this spec when encoding the subject fields from the
Certificatespec. For example, the order of the RDN sequence may not be preserved. This is because cert-manager uses Go's libraries for X.509 certificates, and the Go libraries don't preserve ordering.For the vast majority of users this does not matter, but there are specific cases that require defining the exact ordered RDN sequence. For example, if the certificate is used for LDAP authentication and the RDN sequence represents a location in LDAP directory tree. See
cert-manager#​3203.For these use cases, a new alpha
LiteralSubjectfield has been added to theCertificatespec where users can pass a literal RDN sequence:To use this field, the alpha feature gate
LiteralCertificateSubjectneeds to be enabled on both the cert-manager controller and webhook. Bear in mind thatspec.literalSubjectis mutually exclusive withspec.commonNameandspec.subject.This feature is aimed at the specific scenario where an exact RDN sequence needs to be defined. We do not intend to deprecate the existing
spec.subjectandspec.commonNamefields and we recommend that folks keep using those fields in all other cases; they're simpler, have better validation and are more obvious to read and change.ingress-shim
CertificateConfigurationcert-manager 1.9 adds the ability to configure an ingress-shim
Certificate'sspec.revisionHistoryLimitandspec.privateKeyvia annotations on theIngressresource.This should allow folks to configure ingress-shim
Certificates according to best practices (i.e by settingCertificate'sspec.privateKey.rotationPolicytoAlways).In the future we would like to design a better mechanism to configure these
Certificates. We advise caution when usingIngressannotations as there is no validation of the annotations atIngresscreation time.Contribution Workflow
Over the past couple of months there have been a number of discussions in regards to contributor experience and project health, partially triggered by the awesome community discussions in cert-manager's KubeCon booth and also by the work done to move cert-manager to CNCF's incubating stage.
For example, we've clarified our feature policy and discussed the process of building cert-manager's roadmap. If you're interested in these topics, we're happy to chat about them!
makeWorkflowcert-manager 1.8 introduced a new
makebased workflow alongside the existing Bazel workflow. The work to improve themakeworkflow was continued in 1.9 and our contributor documentation has been redefined to usemakecommands. This should make building and testing cert-manager easier with faster build and test times, easier debugging and less complexity.As part of this, Bazel has now been fully deprecated for building and testing cert-manager.
As usual, we welcome any feedback in regards to further improving contributor experience.
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!
Configuration
📅 Schedule: Branch creation - "before 11pm" (UTC), 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 these updates again.
This PR has been generated by Mend Renovate. View repository job log here.