ZeroDownTime
/
kubezero
3
0
Fork 0
Code Issues 1 Pull Requests 23 Releases Wiki Activity

chore(deps): update helm release cert-manager to v1.13.2 #133

Merged
stefan merged 1 commits from renovate/kubezero-cert-manager-kubezero-cert-manager-dependencies into master 2023-11-24 16:42:28 +00:00
Conversation 0 Commits 1 Files Changed 1 +2 -2
renovate commented 2023-11-22 18:38:20 +00:00
Member
Copy Link

This PR contains the following updates:

Package Update Change
cert-manager minor v1.12.3 -> v1.13.2

Release Notes

cert-manager/cert-manager (cert-manager)

v1.13.2

Compare Source

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

v1.13.2 fixes some CVE alerts and contains fixes for:

  1. a CertificateRequest runaway situation in case two Certificate resources point to the same Secret target resource
  2. a small bug in the Helm chart (feature gate options)
  3. a Venafi issuer bug
⚠️ READ https://github.com/cert-manager/cert-manager/releases/tag/v1.13.0 before you upgrade from a < v1.13 version!

Changes since v1.13.1

Bug or Regression
  • Bump golang.org/x/net v0.15.0 => v0.17.0 as part of addressing CVE-2023-44487 / CVE-2023-39325 (#​6432, @​SgtCoDFish)
  • BUGFIX[helm]: Fix issue where webhook feature gates were only set if controller feature gates are set. (#​6381, @​asapekia)
  • Fix runaway bug caused by multiple Certificate resources that point to the same Secret resource. (#​6425, @​inteon)
  • The Venafi issuer now properly resets the certificate and should no longer get 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.. (#​6402, @​maelvls)
Other (Cleanup or Flake)

v1.13.1

Compare Source

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

v1.13.1 contains a bugfix for a name collision bug in the StableCertificateRequestName feature that was enabled by default in v1.13.0.

⚠️ READ https://github.com/cert-manager/cert-manager/releases/tag/v1.13.0 before you upgrade from a < v1.13 version!

Changes since v1.13.0

Bug or Regression
  • BUGFIX: fix CertificateRequest name collision bug in StableCertificateRequestName feature. (#​6358, @​jetstack-bot)
Other (Cleanup or Flake)

v1.13.0

Compare Source

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

This is the 1.13 release of cert-manager!

cert-manager 1.13 brings support for DNS over HTTPS, support for loading options from a versioned
config file for the cert-manager controller, and more. This release also includes the promotion of
the StableCertificateRequestName and SecretsFilteredCaching feature gates to Beta.

Known issues

The StableCertificateRequestName that was promoted to Beta contains a "name collision" bug: https://github.com/cert-manager/cert-manager/issues/6342
This is fixed in v1.13.1+

Breaking Changes (You MUST read this before you upgrade!)

  1. IMPORTANT NOTE: If upgrading from a version below v1.12, upgrade to the latest v1.12 release before upgrading to v1.13. Otherwise, some certificates may be unexpectedly re-issued (see https://github.com/cert-manager/cert-manager/issues/6494#issuecomment-1816112309)
  2. BREAKING : If you deploy cert-manager using helm and have .featureGates value set, the features defined there will no longer be passed to cert-manager webhook, only to cert-manager controller. Use webhook.featureGates field instead to define features to be enabled on webhook. (#​6093, @​irbekrm)
  3. Potentially breaking: If you were, for some reason, passing cert-manager controller's features to webhook's --feature-gates flag, this will now break (unless the webhook actually has a feature by that name). (#​6093, @​irbekrm)
  4. Potentially breaking: Webhook validation of CertificateRequest resources is stricter now: all KeyUsages and ExtendedKeyUsages must be defined directly in the CertificateRequest resource, the encoded CSR can never contain more usages that defined there. (#​6182, @​inteon)

Community

Welcome to these new cert-manager members (more info - https://github.com/cert-manager/cert-manager/pull/6260):
@​jsoref
@​FlorianLiebhart
@​hawksight
@​erikgb

Thanks again to all open-source contributors with commits in this release, including:
@​AcidLeroy
@​FlorianLiebhart
@​lucacome
@​cypres
@​erikgb
@​ubergesundheit
@​jkroepke
@​jsoref
@​gdvalle
@​rouke-broersma
@​schrodit
@​zhangzhiqiangcs
@​arukiidou
@​hawksight
@​Richardds
@​kahirokunn

Thanks also to the following cert-manager maintainers for their contributions during this release:
@​SgtCoDFish
@​maelvls
@​irbekrm
@​inteon

Equally thanks to everyone who provided feedback, helped users and raised issues on Github and Slack and joined our meetings!

Special thanks to @​AcidLeroy for adding "load options from a versioned config file" support for the cert-manager controller! This has been on our wishlist for a very long time. (see https://github.com/cert-manager/cert-manager/pull/5337)

Also, thanks a lot to @​FlorianLiebhart for adding support for DNS over HTTPS for the ACME DNS self-check. This is very useful in case all traffic must be HTTP(S) trafic, eg. when using a HTTPS_PROXY. (see https://github.com/cert-manager/cert-manager/pull/5003)

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 Venafi for contributing developer time and resources towards the continued maintenance of cert-manager projects.

Changes since v1.12.0

Feature
  • Add support for logging options to webhook config file. (#​6243, @​inteon)
  • Add view permissions to the well-known (Openshift) user-facing cluster-reader aggregated cluster role (#​6241, @​erikgb)
  • Certificate Shim: distinguish dns names and ip address in certificate (#​6267, @​zhangzhiqiangcs)
  • Cmctl can now be imported by third parties. (#​6049, @​SgtCoDFish)
  • Make enableServiceLinks configurable for all Deployments and startupapicheck Job in Helm chart. (#​6292, @​ubergesundheit)
  • Promoted the StableCertificateRequestName and SecretsFilteredCaching feature gates to Beta (enabled by default). (#​6298, @​inteon)
  • The cert-manager controller options are now configurable using a configuration file. (#​5337, @​AcidLeroy)
  • The pki CertificateTemplate functions now perform validation of the CSR blob, making sure we sign a Certificate that matches the IsCA and (Extended)KeyUsages that are defined in the CertificateRequest resource. (#​6199, @​inteon)
  • helm] Add prometheus.servicemonitor.endpointAdditionalProperties to define additional properties on a ServiceMonitor endpoint, e.g. relabelings ([#&#8203;6110](https://github.com/cert-manager/cert-manager/issues/6110), [@&#8203;jkroepke](https://github.com/jkroepke))
Design
  • DNS over HTTPS (DoH) is now possible for doing the self-checks during the ACME verification.
    The DNS check method to be used is controlled through the command line flag: --dns01-recursive-nameservers-only=true in combination with --dns01-recursive-nameservers=https://<DoH-endpoint> (e.g. https://8.8.8.8/dns-query). It keeps using DNS lookup as a default method. (#​5003, @​FlorianLiebhart)
Bug or Regression
  • Allow overriding default pdb .minAvailable with .maxUnavailable without setting .minAvailable to null (#​6087, @​rouke-broersma)
  • BUGFIX: cmctl check api --wait 0 exited without output and exit code 1; we now make sure we perform the API check at least once and return with the correct error code (#​6109, @​inteon)
  • BUGFIX: the issuer and certificate-name annotations on a Secret were incorrectly updated when other fields are changed. (#​6147, @​inteon)
  • BUGFIX[cainjector]: 1-character bug was causing invalid log messages and a memory leak (#​6232, @​inteon)
  • Fix CloudDNS issuers stuck in propagation check, when multiple instances are issuing for the same FQDN (#​6088, @​cypres)
  • Fix indentation of Webhook NetworkPolicy matchLabels in helm chart. (#​6220, @​ubergesundheit)
  • Fixed Cloudflare DNS01 challenge provider race condition when validating multiple domains (#​6191, @​Richardds)
  • Fixes a bug where webhook was pulling in controller's feature gates.
    ⚠️ ⚠️ BREAKING ⚠️ ⚠️ : If you deploy cert-manager using helm and have .featureGates value set, the features defined there will no longer be passed to cert-manager webhook, only to cert-manager controller. Use webhook.featureGates field instead to define features to be enabled on webhook.
    ⚠️Potentially breaking: If you were, for some reason, passing cert-manager controller's features to webhook's --feature-gates flag, this will now break (unless the webhook actually has a feature by that name). (#​6093, @​irbekrm)
  • Fixes an issue where cert-manager would incorrectly reject two IP addresses as being unequal when they should have compared equal. This would be most noticeable when using an IPv6 address which doesn't match how Go's net.IP.String() function would have printed that address. (#​6293, @​SgtCoDFish)
  • We disabled the enableServiceLinks option for our ACME http solver pods, because the option caused the pod to be in a crash loop in a cluster with lot of services. (#​6143, @​schrodit)
  • ⚠️Potentially breaking: Webhook validation of CertificateRequest resources is stricter now: all KeyUsages and ExtendedKeyUsages must be defined directly in the CertificateRequest resource, the encoded CSR can never contain more usages that defined there. (#​6182, @​inteon)
Other (Cleanup or Flake)
  • A subset of the klogs flags have been deprecated and will be removed in the future. (#​5879, @​maelvls)
  • All service links in helm chart deployments have been disabled. (#​6144, @​schrodit)
  • Cert-manager will now re-issue a certificate if the public key in the latest CertificateRequest resource linked to a Certificate resource does not match the public key of the key encoded in the Secret linked to that Certificate resource (#​6168, @​inteon)
  • Chore: When hostNetwork is enabled, dnsPolicy is now set to ClusterFirstWithHostNet. (#​6156, @​kahirokunn)
  • Cleanup the controller configfile structure by introducing sub-structs. (#​6242, @​inteon)
  • Don't run API Priority and Fairness controller in webhook's extension apiserver (#​6085, @​irbekrm)
  • Helm: Add apache 2.0 license annotation (#​6225, @​arukiidou)
  • Make apis/acme/v1/ACMEIssuer.PreferredChain optional in JSON serialization. (#​6034, @​gdvalle)
  • The SecretPostIssuancePolicyChain now also makes sure that the cert-manager.io/common-name, cert-manager.io/alt-names, ... annotations on Secrets are kept at their correct value. (#​6176, @​inteon)
  • The cmctl logging has been improved and support for json logging has been added. (#​6247, @​inteon)
  • Updates Kubernetes libraries to v0.27.2. (#​6077, @​lucacome)
  • Updates Kubernetes libraries to v0.27.4. (#​6227, @​lucacome)
  • We now only check that the issuer name, kind and group annotations on a Secret match in case those annotations are set. (#​6152, @​inteon)

v1.12.6

Compare Source

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

v1.12.6 fixes some CVE alerts and a Venafi issuer bug.

Changes since v1.12.5

Bug or Regression
  • Bump golang.org/x/net v0.15.0 => v0.17.0 as part of addressing CVE-2023-44487 / CVE-2023-39325 (#​6431, @​SgtCoDFish)
  • The Venafi issuer now properly resets the certificate and should no longer get 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.. (#​6401, @​maelvls)
Other (Cleanup or Flake)

Known bugs

If you misconfigure two Certificate resources to have the same target Secret resource, cert-manager will generate a MANY CertificateRequests, possibly causing high CPU usage and/ or high costs due to the large number of certificates issued (see https://github.com/cert-manager/cert-manager/pull/6406).
This problem was resolved in v1.13.2, but the fix cannot be backported to v1.12.x. We recommend using v1.12.x with caution (avoid misconfigured Certificate resources) or upgrading to v1.13.2.

v1.12.5

Compare Source

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

v1.12.5 contains a backport for a name collision bug that was found in v1.13.0

Changes since v1.12.4

Bug or Regression
  • BUGFIX: fix CertificateRequest name collision bug in StableCertificateRequestName feature. (#​6359, @​jetstack-bot)
Other (Cleanup or Flake)

v1.12.4

Compare Source

v1.12.4 contains an important security fix that addresses CVE-2023-29409.

Changes since v1.12.3

  • Fixes an issue where cert-manager would incorrectly reject two IP addresses as being unequal when they should have compared equal. This would be most noticeable when using an IPv6 address which doesn't match how Go's net.IP.String() function would have printed that address. (#​6297, @​SgtCoDFish)
  • Use Go 1.20.7 to fix a security issue in Go's crypto/tls library. (#​6318, @​maelvls)

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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [cert-manager](https://github.com/cert-manager/cert-manager) | minor | `v1.12.3` -> `v1.13.2` | --- ### Release Notes <details> <summary>cert-manager/cert-manager (cert-manager)</summary> ### [`v1.13.2`](https://github.com/cert-manager/cert-manager/releases/tag/v1.13.2) [Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.13.1...v1.13.2) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.13.2 fixes some CVE alerts and contains fixes for: 1. a CertificateRequest runaway situation in case two Certificate resources point to the same Secret target resource 2. a small bug in the Helm chart (feature gate options) 3. a Venafi issuer bug ##### ⚠️ READ https://github.com/cert-manager/cert-manager/releases/tag/v1.13.0 before you upgrade from a < v1.13 version! #### Changes since v1.13.1 ##### Bug or Regression - Bump golang.org/x/net v0.15.0 => v0.17.0 as part of addressing CVE-2023-44487 / CVE-2023-39325 ([#&#8203;6432](https://github.com/cert-manager/cert-manager/issues/6432), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish)) - BUGFIX\[helm]: Fix issue where webhook feature gates were only set if controller feature gates are set. ([#&#8203;6381](https://github.com/cert-manager/cert-manager/issues/6381), [@&#8203;asapekia](https://github.com/asapekia)) - Fix runaway bug caused by multiple Certificate resources that point to the same Secret resource. ([#&#8203;6425](https://github.com/cert-manager/cert-manager/issues/6425), [@&#8203;inteon](https://github.com/inteon)) - The Venafi issuer now properly resets the certificate and should no longer get 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.`. ([#&#8203;6402](https://github.com/cert-manager/cert-manager/issues/6402), [@&#8203;maelvls](https://github.com/maelvls)) ##### Other (Cleanup or Flake) - Bump go to 1.20.10 to address CVE-2023-39325. Also bumps base images. ([#&#8203;6411](https://github.com/cert-manager/cert-manager/issues/6411), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish)) ### [`v1.13.1`](https://github.com/cert-manager/cert-manager/releases/tag/v1.13.1) [Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.13.0...v1.13.1) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.13.1 contains a bugfix for a name collision bug in the StableCertificateRequestName feature that was enabled by default in v1.13.0. ##### ⚠️ READ https://github.com/cert-manager/cert-manager/releases/tag/v1.13.0 before you upgrade from a < v1.13 version! #### Changes since v1.13.0 ##### Bug or Regression - BUGFIX: fix CertificateRequest name collision bug in StableCertificateRequestName feature. ([#&#8203;6358](https://github.com/cert-manager/cert-manager/issues/6358), [@&#8203;jetstack-bot](https://github.com/jetstack-bot)) ##### Other (Cleanup or Flake) - Upgrade `github.com/emicklei/go-restful/v3` to `v3.11.0` because `v3.10.2` is labeled as "DO NOT USE". ([#&#8203;6368](https://github.com/cert-manager/cert-manager/issues/6368), [@&#8203;inteon](https://github.com/inteon)) - Upgrade Go from 1.20.7 to 1.20.8. ([#&#8203;6370](https://github.com/cert-manager/cert-manager/issues/6370), [@&#8203;jetstack-bot](https://github.com/jetstack-bot)) ### [`v1.13.0`](https://github.com/cert-manager/cert-manager/releases/tag/v1.13.0) [Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.12.6...v1.13.0) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. This is the 1.13 release of cert-manager! cert-manager 1.13 brings support for DNS over HTTPS, support for loading options from a versioned config file for the cert-manager controller, and more. This release also includes the promotion of the StableCertificateRequestName and SecretsFilteredCaching feature gates to Beta. #### Known issues The `StableCertificateRequestName` that was promoted to Beta contains a "name collision" bug: https://github.com/cert-manager/cert-manager/issues/6342 This is fixed in v1.13.1+ #### Breaking Changes (You MUST read this before you upgrade!) 1. **IMPORTANT NOTE**: If upgrading from a version below v1.12, upgrade to the latest v1.12 release before upgrading to v1.13. Otherwise, some certificates may be unexpectedly re-issued (see https://github.com/cert-manager/cert-manager/issues/6494#issuecomment-1816112309) 2. **BREAKING** : If you deploy cert-manager using helm and have `.featureGates` value set, the features defined there will no longer be passed to cert-manager webhook, only to cert-manager controller. Use `webhook.featureGates` field instead to define features to be enabled on webhook. ([#&#8203;6093](https://github.com/cert-manager/cert-manager/issues/6093), [@&#8203;irbekrm](https://github.com/irbekrm)) 3. **Potentially breaking**: If you were, for some reason, passing cert-manager controller's features to webhook's `--feature-gates` flag, this will now break (unless the webhook actually has a feature by that name). ([#&#8203;6093](https://github.com/cert-manager/cert-manager/issues/6093), [@&#8203;irbekrm](https://github.com/irbekrm)) 4. **Potentially breaking**: Webhook validation of CertificateRequest resources is stricter now: all KeyUsages and ExtendedKeyUsages must be defined directly in the CertificateRequest resource, the encoded CSR can never contain more usages that defined there. ([#&#8203;6182](https://github.com/cert-manager/cert-manager/issues/6182), [@&#8203;inteon](https://github.com/inteon)) #### Community Welcome to these new cert-manager members (more info - https://github.com/cert-manager/cert-manager/pull/6260): [@&#8203;jsoref](https://github.com/jsoref) [@&#8203;FlorianLiebhart](https://github.com/FlorianLiebhart) [@&#8203;hawksight](https://github.com/hawksight) [@&#8203;erikgb](https://github.com/erikgb) Thanks again to all open-source contributors with commits in this release, including: [@&#8203;AcidLeroy](https://github.com/AcidLeroy) [@&#8203;FlorianLiebhart](https://github.com/FlorianLiebhart) [@&#8203;lucacome](https://github.com/lucacome) [@&#8203;cypres](https://github.com/cypres) [@&#8203;erikgb](https://github.com/erikgb) [@&#8203;ubergesundheit](https://github.com/ubergesundheit) [@&#8203;jkroepke](https://github.com/jkroepke) [@&#8203;jsoref](https://github.com/jsoref) [@&#8203;gdvalle](https://github.com/gdvalle) [@&#8203;rouke-broersma](https://github.com/rouke-broersma) [@&#8203;schrodit](https://github.com/schrodit) [@&#8203;zhangzhiqiangcs](https://github.com/zhangzhiqiangcs) [@&#8203;arukiidou](https://github.com/arukiidou) [@&#8203;hawksight](https://github.com/hawksight) [@&#8203;Richardds](https://github.com/Richardds) [@&#8203;kahirokunn](https://github.com/kahirokunn) Thanks also to the following cert-manager maintainers for their contributions during this release: [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish) [@&#8203;maelvls](https://github.com/maelvls) [@&#8203;irbekrm](https://github.com/irbekrm) [@&#8203;inteon](https://github.com/inteon) Equally thanks to everyone who provided feedback, helped users and raised issues on Github and Slack and joined our meetings! Special thanks to [@&#8203;AcidLeroy](https://github.com/AcidLeroy) for adding "load options from a versioned config file" support for the cert-manager controller! This has been on our wishlist for a very long time. (see https://github.com/cert-manager/cert-manager/pull/5337) Also, thanks a lot to [@&#8203;FlorianLiebhart](https://github.com/FlorianLiebhart) for adding support for DNS over HTTPS for the ACME DNS self-check. This is very useful in case all traffic must be HTTP(S) trafic, eg. when using a HTTPS_PROXY. (see https://github.com/cert-manager/cert-manager/pull/5003) Thanks also to the [CNCF](https://www.cncf.io/), 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](https://github.com/cert-manager/aws-privateca-issuer). In addition, massive thanks to [Venafi](https://www.venafi.com/) for contributing developer time and resources towards the continued maintenance of cert-manager projects. #### Changes since v1.12.0 ##### Feature - Add support for logging options to webhook config file. ([#&#8203;6243](https://github.com/cert-manager/cert-manager/issues/6243), [@&#8203;inteon](https://github.com/inteon)) - Add view permissions to the well-known (Openshift) user-facing `cluster-reader` aggregated cluster role ([#&#8203;6241](https://github.com/cert-manager/cert-manager/issues/6241), [@&#8203;erikgb](https://github.com/erikgb)) - Certificate Shim: distinguish dns names and ip address in certificate ([#&#8203;6267](https://github.com/cert-manager/cert-manager/issues/6267), [@&#8203;zhangzhiqiangcs](https://github.com/zhangzhiqiangcs)) - Cmctl can now be imported by third parties. ([#&#8203;6049](https://github.com/cert-manager/cert-manager/issues/6049), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish)) - Make `enableServiceLinks` configurable for all Deployments and `startupapicheck` Job in Helm chart. ([#&#8203;6292](https://github.com/cert-manager/cert-manager/issues/6292), [@&#8203;ubergesundheit](https://github.com/ubergesundheit)) - Promoted the StableCertificateRequestName and SecretsFilteredCaching feature gates to Beta (enabled by default). ([#&#8203;6298](https://github.com/cert-manager/cert-manager/issues/6298), [@&#8203;inteon](https://github.com/inteon)) - The cert-manager controller options are now configurable using a configuration file. ([#&#8203;5337](https://github.com/cert-manager/cert-manager/issues/5337), [@&#8203;AcidLeroy](https://github.com/AcidLeroy)) - The pki CertificateTemplate functions now perform validation of the CSR blob, making sure we sign a Certificate that matches the IsCA and (Extended)KeyUsages that are defined in the CertificateRequest resource. ([#&#8203;6199](https://github.com/cert-manager/cert-manager/issues/6199), [@&#8203;inteon](https://github.com/inteon)) - \[helm] Add prometheus.servicemonitor.endpointAdditionalProperties to define additional properties on a ServiceMonitor endpoint, e.g. relabelings ([#&#8203;6110](https://github.com/cert-manager/cert-manager/issues/6110), [@&#8203;jkroepke](https://github.com/jkroepke)) ##### Design - DNS over HTTPS (DoH) is now possible for doing the self-checks during the ACME verification. The DNS check method to be used is controlled through the command line flag: `--dns01-recursive-nameservers-only=true` in combination with `--dns01-recursive-nameservers=https://<DoH-endpoint>` (e.g. `https://8.8.8.8/dns-query`). It keeps using DNS lookup as a default method. ([#&#8203;5003](https://github.com/cert-manager/cert-manager/issues/5003), [@&#8203;FlorianLiebhart](https://github.com/FlorianLiebhart)) ##### Bug or Regression - Allow overriding default pdb .minAvailable with .maxUnavailable without setting .minAvailable to null ([#&#8203;6087](https://github.com/cert-manager/cert-manager/issues/6087), [@&#8203;rouke-broersma](https://github.com/rouke-broersma)) - BUGFIX: `cmctl check api --wait 0` exited without output and exit code 1; we now make sure we perform the API check at least once and return with the correct error code ([#&#8203;6109](https://github.com/cert-manager/cert-manager/issues/6109), [@&#8203;inteon](https://github.com/inteon)) - BUGFIX: the issuer and certificate-name annotations on a Secret were incorrectly updated when other fields are changed. ([#&#8203;6147](https://github.com/cert-manager/cert-manager/issues/6147), [@&#8203;inteon](https://github.com/inteon)) - BUGFIX\[cainjector]: 1-character bug was causing invalid log messages and a memory leak ([#&#8203;6232](https://github.com/cert-manager/cert-manager/issues/6232), [@&#8203;inteon](https://github.com/inteon)) - Fix CloudDNS issuers stuck in propagation check, when multiple instances are issuing for the same FQDN ([#&#8203;6088](https://github.com/cert-manager/cert-manager/issues/6088), [@&#8203;cypres](https://github.com/cypres)) - Fix indentation of Webhook NetworkPolicy matchLabels in helm chart. ([#&#8203;6220](https://github.com/cert-manager/cert-manager/issues/6220), [@&#8203;ubergesundheit](https://github.com/ubergesundheit)) - Fixed Cloudflare DNS01 challenge provider race condition when validating multiple domains ([#&#8203;6191](https://github.com/cert-manager/cert-manager/issues/6191), [@&#8203;Richardds](https://github.com/Richardds)) - Fixes a bug where webhook was pulling in controller's feature gates. **⚠️ ⚠️ BREAKING ⚠️ ⚠️** : If you deploy cert-manager using helm and have `.featureGates` value set, the features defined there will no longer be passed to cert-manager webhook, only to cert-manager controller. Use `webhook.featureGates` field instead to define features to be enabled on webhook. **⚠️Potentially breaking**: If you were, for some reason, passing cert-manager controller's features to webhook's `--feature-gates` flag, this will now break (unless the webhook actually has a feature by that name). ([#&#8203;6093](https://github.com/cert-manager/cert-manager/issues/6093), [@&#8203;irbekrm](https://github.com/irbekrm)) - Fixes an issue where cert-manager would incorrectly reject two IP addresses as being unequal when they should have compared equal. This would be most noticeable when using an IPv6 address which doesn't match how Go's `net.IP.String()` function would have printed that address. ([#&#8203;6293](https://github.com/cert-manager/cert-manager/issues/6293), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish)) - We disabled the `enableServiceLinks` option for our ACME http solver pods, because the option caused the pod to be in a crash loop in a cluster with lot of services. ([#&#8203;6143](https://github.com/cert-manager/cert-manager/issues/6143), [@&#8203;schrodit](https://github.com/schrodit)) - **⚠️Potentially breaking**: Webhook validation of CertificateRequest resources is stricter now: all KeyUsages and ExtendedKeyUsages must be defined directly in the CertificateRequest resource, the encoded CSR can never contain more usages that defined there. ([#&#8203;6182](https://github.com/cert-manager/cert-manager/issues/6182), [@&#8203;inteon](https://github.com/inteon)) ##### Other (Cleanup or Flake) - A subset of the klogs flags have been deprecated and will be removed in the future. ([#&#8203;5879](https://github.com/cert-manager/cert-manager/issues/5879), [@&#8203;maelvls](https://github.com/maelvls)) - All service links in helm chart deployments have been disabled. ([#&#8203;6144](https://github.com/cert-manager/cert-manager/issues/6144), [@&#8203;schrodit](https://github.com/schrodit)) - Cert-manager will now re-issue a certificate if the public key in the latest CertificateRequest resource linked to a Certificate resource does not match the public key of the key encoded in the Secret linked to that Certificate resource ([#&#8203;6168](https://github.com/cert-manager/cert-manager/issues/6168), [@&#8203;inteon](https://github.com/inteon)) - Chore: When hostNetwork is enabled, dnsPolicy is now set to ClusterFirstWithHostNet. ([#&#8203;6156](https://github.com/cert-manager/cert-manager/issues/6156), [@&#8203;kahirokunn](https://github.com/kahirokunn)) - Cleanup the controller configfile structure by introducing sub-structs. ([#&#8203;6242](https://github.com/cert-manager/cert-manager/issues/6242), [@&#8203;inteon](https://github.com/inteon)) - Don't run API Priority and Fairness controller in webhook's extension apiserver ([#&#8203;6085](https://github.com/cert-manager/cert-manager/issues/6085), [@&#8203;irbekrm](https://github.com/irbekrm)) - Helm: Add apache 2.0 license annotation ([#&#8203;6225](https://github.com/cert-manager/cert-manager/issues/6225), [@&#8203;arukiidou](https://github.com/arukiidou)) - Make apis/acme/v1/ACMEIssuer.PreferredChain optional in JSON serialization. ([#&#8203;6034](https://github.com/cert-manager/cert-manager/issues/6034), [@&#8203;gdvalle](https://github.com/gdvalle)) - The SecretPostIssuancePolicyChain now also makes sure that the `cert-manager.io/common-name`, `cert-manager.io/alt-names`, ... annotations on Secrets are kept at their correct value. ([#&#8203;6176](https://github.com/cert-manager/cert-manager/issues/6176), [@&#8203;inteon](https://github.com/inteon)) - The cmctl logging has been improved and support for json logging has been added. ([#&#8203;6247](https://github.com/cert-manager/cert-manager/issues/6247), [@&#8203;inteon](https://github.com/inteon)) - Updates Kubernetes libraries to `v0.27.2`. ([#&#8203;6077](https://github.com/cert-manager/cert-manager/issues/6077), [@&#8203;lucacome](https://github.com/lucacome)) - Updates Kubernetes libraries to `v0.27.4`. ([#&#8203;6227](https://github.com/cert-manager/cert-manager/issues/6227), [@&#8203;lucacome](https://github.com/lucacome)) - We now only check that the issuer name, kind and group annotations on a Secret match in case those annotations are set. ([#&#8203;6152](https://github.com/cert-manager/cert-manager/issues/6152), [@&#8203;inteon](https://github.com/inteon)) ### [`v1.12.6`](https://github.com/cert-manager/cert-manager/releases/tag/v1.12.6) [Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.12.5...v1.12.6) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.12.6 fixes some CVE alerts and a Venafi issuer bug. #### Changes since v1.12.5 ##### Bug or Regression - Bump golang.org/x/net v0.15.0 => v0.17.0 as part of addressing CVE-2023-44487 / CVE-2023-39325 ([#&#8203;6431](https://github.com/cert-manager/cert-manager/issues/6431), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish)) - The Venafi issuer now properly resets the certificate and should no longer get 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.`. ([#&#8203;6401](https://github.com/cert-manager/cert-manager/issues/6401), [@&#8203;maelvls](https://github.com/maelvls)) ##### Other (Cleanup or Flake) - Bump go to 1.20.10 to address CVE-2023-39325. Also bumps base images. ([#&#8203;6412](https://github.com/cert-manager/cert-manager/issues/6412), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish)) #### Known bugs If you misconfigure two Certificate resources to have the same target Secret resource, cert-manager will generate a MANY CertificateRequests, possibly causing high CPU usage and/ or high costs due to the large number of certificates issued (see https://github.com/cert-manager/cert-manager/pull/6406). This problem was resolved in v1.13.2, but the fix cannot be backported to v1.12.x. We recommend using v1.12.x with caution (avoid misconfigured Certificate resources) or upgrading to v1.13.2. ### [`v1.12.5`](https://github.com/cert-manager/cert-manager/releases/tag/v1.12.5) [Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.12.4...v1.12.5) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. v1.12.5 contains a backport for a name collision bug that was found in v1.13.0 #### Changes since v1.12.4 ##### Bug or Regression - BUGFIX: fix CertificateRequest name collision bug in StableCertificateRequestName feature. ([#&#8203;6359](https://github.com/cert-manager/cert-manager/issues/6359), [@&#8203;jetstack-bot](https://github.com/jetstack-bot)) ##### Other (Cleanup or Flake) - Updated base images to the latest version. ([#&#8203;6372](https://github.com/cert-manager/cert-manager/issues/6372), [@&#8203;inteon](https://github.com/inteon)) - Upgrade Go from 1.20.7 to 1.20.8. ([#&#8203;6371](https://github.com/cert-manager/cert-manager/issues/6371), [@&#8203;jetstack-bot](https://github.com/jetstack-bot)) ### [`v1.12.4`](https://github.com/cert-manager/cert-manager/releases/tag/v1.12.4) [Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.12.3...v1.12.4) v1.12.4 contains an important security fix that addresses [CVE-2023-29409](https://cve.report/CVE-2023-29409). #### Changes since v1.12.3 - Fixes an issue where cert-manager would incorrectly reject two IP addresses as being unequal when they should have compared equal. This would be most noticeable when using an IPv6 address which doesn't match how Go's `net.IP.String()` function would have printed that address. ([#&#8203;6297](https://github.com/cert-manager/cert-manager/issues/6297), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish)) - Use Go 1.20.7 to fix a security issue in Go's `crypto/tls` library. ([#&#8203;6318](https://github.com/cert-manager/cert-manager/issues/6318), [@&#8203;maelvls](https://github.com/maelvls)) </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy42NC4zIiwidXBkYXRlZEluVmVyIjoiMzcuNjQuMyIsInRhcmdldEJyYW5jaCI6Im1hc3RlciJ9-->
renovate added the
renovate
 label 2023-11-22 18:38:20 +00:00
renovate added 1 commit 2023-11-22 18:38:21 +00:00
stefan merged commit d25a76b526 into master 2023-11-24 16:42:28 +00:00
stefan deleted branch renovate/kubezero-cert-manager-kubezero-cert-manager-dependencies 2023-11-24 16:42:30 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
renovate

Dependency via Renovate

No Label
renovate
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ZeroDownTime/kubezero#133
No description provided.
Delete Branch "renovate/kubezero-cert-manager-kubezero-cert-manager-dependencies"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?