openstack-k8s-ci-robot
commented
2 days ago ℹ Artifact update notice
File name: apis/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):
- 1 additional dependency was updated
Details:
| Package | Change |
|---|---|
sigs.k8s.io/gateway-api |
v0.8.0 -> v1.0.0 |
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):
- 1 additional dependency was updated
Details:
| Package | Change |
|---|---|
sigs.k8s.io/gateway-api |
v0.8.0 -> v1.0.0 |
openshift-ci[bot]
softwarefactory-project-zuul[bot]
bshephar
This PR contains the following updates:
v1.13.6->v1.14.7Release Notes
cert-manager/cert-manager (github.com/cert-manager/cert-manager)
### [`v1.14.7`](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.7) [Compare Source](https://redirect.github.com/cert-manager/cert-manager/compare/v1.14.6...v1.14.7) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. ##### 📜 Changes since [v1.14.6](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.6) ##### Bugfixes - BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. ([#7113](https://redirect.github.com/cert-manager/cert-manager/issues/7113), [@cert-manager-bot](https://redirect.github.com/cert-manager-bot)) ##### Other (Cleanup or Flake) - Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to address CVE-2024-35255 ([#7093](https://redirect.github.com/cert-manager/cert-manager/issues/7093), [@ThatsMrTalbot](https://redirect.github.com/ThatsMrTalbot)) ### [`v1.14.6`](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.6) [Compare Source](https://redirect.github.com/cert-manager/cert-manager/compare/v1.14.5...v1.14.6) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. ##### 📜 Changes since [v1.14.5](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.5) ##### Other (Cleanup or Flake) - Upgrade Go to 1.21.10, fixing GO-2024-2824 (https://github.com/advisories/GHSA-2jwv-jmq4-4j3r). ([#7008](https://redirect.github.com/cert-manager/cert-manager/issues/7008), [@inteon](https://redirect.github.com/inteon)) - Helm: the cainjector ConfigMap was not mounted in the cainjector deployment. ([#7053](https://redirect.github.com/cert-manager/cert-manager/issues/7053), [@cert-manager-bot](https://redirect.github.com/cert-manager-bot)) - Updated Go to 1.21.11 bringing in security fixes for archive/zip and net/netip. ([#7076](https://redirect.github.com/cert-manager/cert-manager/issues/7076), [@ThatsMrTalbot](https://redirect.github.com/ThatsMrTalbot)) ### [`v1.14.5`](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.5) [Compare Source](https://redirect.github.com/cert-manager/cert-manager/compare/v1.14.4...v1.14.5) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. `v1.14.5` fixes a bug in the DigitalOcean DNS-01 provider which could cause incorrect DNS records to be deleted when using a domain with a CNAME. Special thanks to [@BobyMCbobs](https://redirect.github.com/BobyMCbobs) for reporting this issue and testing the fix! It also patches CVE-2023-45288. ##### 📜 Changes since [v1.14.4](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.4) - ACME Issuer (Let's Encrypt): wrong certificate chain may be used if `preferredChain` is configured: see [1.14 release notes](./release-notes-1.14.md#known-issues) for more information. ##### Changes ##### Bug or Regression - DigitalOcean: Ensure that only TXT records are considered for deletion when cleaning up after an ACME challenge ([#6893](https://redirect.github.com/cert-manager/cert-manager/issues/6893) , [@SgtCoDFish](https://redirect.github.com/SgtCoDFish)) - Bump golang.org/x/net to address [CVE-2023-45288](https://nvd.nist.gov/vuln/detail/CVE-2023-45288) ([#6931](https://redirect.github.com/cert-manager/cert-manager/issues/6931) , [@SgtCoDFish](https://redirect.github.com/SgtCoDFish)) ### [`v1.14.4`](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.4) [Compare Source](https://redirect.github.com/cert-manager/cert-manager/compare/v1.14.3...v1.14.4) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions. ##### ⚠️ Known Issues - ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see [release docs](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14/#acme-issuer-lets-encrypt-wrong-certificate-chain-may-be-used-if-preferredchain-is-configured---6755-6757) for more info and mitigations ##### ℹ️ Documentation [Release notes](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14) [Upgrade notes](https://cert-manager.io/docs/releases/upgrading/upgrading-1.13-1.14) [Installation instructions](https://cert-manager.io/docs/installation/) ##### 🔧 Breaking changes See Breaking changes in [v1.14.0 release notes](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.0) ##### 📜 Changes since v1.14.3 ##### Bug or Regression - Allow `cert-manager.io/allow-direct-injection` in annotations ([#6809](https://redirect.github.com/cert-manager/cert-manager/issues/6809), [@jetstack-bot](https://redirect.github.com/jetstack-bot)) - BUGFIX: JKS and PKCS12 stores now contain the full set of CAs specified by an issuer ([#6812](https://redirect.github.com/cert-manager/cert-manager/issues/6812), [@jetstack-bot](https://redirect.github.com/jetstack-bot)) - BUGFIX: cainjector leaderelection flag/ config option defaults are missing ([#6819](https://redirect.github.com/cert-manager/cert-manager/issues/6819), [@jetstack-bot](https://redirect.github.com/jetstack-bot)) ##### Other (Cleanup or Flake) - Bump base images. ([#6842](https://redirect.github.com/cert-manager/cert-manager/issues/6842), [@inteon](https://redirect.github.com/inteon)) - Upgrade Helm: fix CVE-2024-26147 alert ([#6834](https://redirect.github.com/cert-manager/cert-manager/issues/6834), [@inteon](https://redirect.github.com/inteon)) - Upgrade go to 1.21.8: fixes CVE-2024-24783 ([#6825](https://redirect.github.com/cert-manager/cert-manager/issues/6825), [@jetstack-bot](https://redirect.github.com/jetstack-bot)) - Upgrade google.golang.org/protobuf: fixing GO-2024-2611 ([#6829](https://redirect.github.com/cert-manager/cert-manager/issues/6829), [@inteon](https://redirect.github.com/inteon)) ### [`v1.14.3`](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.3) [Compare Source](https://redirect.github.com/cert-manager/cert-manager/compare/v1.14.2...v1.14.3) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions. ##### ⚠️ Known Issues - ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see [release docs](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14/#acme-issuer-lets-encrypt-wrong-certificate-chain-may-be-used-if-preferredchain-is-configured---6755-6757) for more info and mitigations - cainjector leaderelection is incorrectly disabled by default because the flag/ config option defaults are missing ([https://github.com/cert-manager/cert-manager/pull/6819](https://redirect.github.com/cert-manager/cert-manager/pull/6819)) ##### ℹ️ Documentation [Release notes](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14) [Upgrade notes](https://cert-manager.io/docs/releases/upgrading/upgrading-1.13-1.14) [Installation instructions](https://cert-manager.io/docs/installation/) ##### 🔧 Breaking changes See Breaking changes in [v1.14.0 release notes](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.0) ##### 📜 Changes since v1.14.2 ##### Bug or Regression - BUGFIX: Fixes issue with JSON-logging, where only a subset of the log messages were output as JSON. ([#6781](https://redirect.github.com/cert-manager/cert-manager/issues/6781), [@jetstack-bot](https://redirect.github.com/jetstack-bot)) - BUGFIX: LiteralSubjects with a #= value can result in memory issues due to faulty BER parser (github.com/go-asn1-ber/asn1-ber). ([#6774](https://redirect.github.com/cert-manager/cert-manager/issues/6774), [@jetstack-bot](https://redirect.github.com/jetstack-bot)) ### [`v1.14.2`](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.2) [Compare Source](https://redirect.github.com/cert-manager/cert-manager/compare/v1.14.1...v1.14.2) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions. ##### ⚠️ Known Issues - ACME Issuer (Let's Encrypt): wrong certificate chain may be used if `preferredChain` is configured: see [release docs](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14/#acme-issuer-lets-encrypt-wrong-certificate-chain-may-be-used-if-preferredchain-is-configured---6755-6757) for more info and mitigations - Logging-format json sometimes writes plaintext messages (see [https://github.com/cert-manager/cert-manager/issues/6768](https://redirect.github.com/cert-manager/cert-manager/issues/6768)). FIXED in v1.14.3 ##### ℹ️ Documentation [Release notes](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14) [Upgrade notes](https://cert-manager.io/docs/releases/upgrading/upgrading-1.13-1.14) [Installation instructions](https://cert-manager.io/docs/installation/) ##### 🔧 Breaking changes See `Breaking changes` in [v1.14.0 release notes](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.0) ##### 📜 Changes since `v1.14.1` ##### Bug or Regression - BUGFIX: cert-manager CA and SelfSigned issuers incorrectly copied the critical flag from the CSR instead of re-calculating that field themselves. ([#6727](https://redirect.github.com/cert-manager/cert-manager/issues/6727), [@jetstack-bot](https://redirect.github.com/jetstack-bot)) - Helm: Fix a bug in the logic that differentiates between 0 and an empty value. ([#6729](https://redirect.github.com/cert-manager/cert-manager/issues/6729), [@jetstack-bot](https://redirect.github.com/jetstack-bot)) ##### Other (Cleanup or Flake) - Bump golang to 1.21.7 ([#6735](https://redirect.github.com/cert-manager/cert-manager/issues/6735), [@jetstack-bot](https://redirect.github.com/jetstack-bot)) ### [`v1.14.1`](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.1) [Compare Source](https://redirect.github.com/cert-manager/cert-manager/compare/v1.14.0...v1.14.1) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions. > ⚠️ This version has known issues. Please install `v1.14.2` instead. ##### ⚠️ Known Issues (please install `v1.14.2`) - ACME Issuer (Let's Encrypt): wrong certificate chain may be used if `preferredChain` is configured: see [release docs](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14/#acme-issuer-lets-encrypt-wrong-certificate-chain-may-be-used-if-preferredchain-is-configured---6755-6757) for more info and mitigations - In cert-manager v1.14.0 and v1.14.1, the `CA` and `SelfSigned` issuers issue certificates with SANs set to non-critical even when the subject is empty. It incorrectly copies the critical field from the CSR. ##### 🔧 Breaking changes See `Breaking changes` in [v1.14.0 release notes](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.0) ##### ℹ️ Documentation - [Release notes](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14) - [Upgrade notes](https://cert-manager.io/docs/releases/upgrading/upgrading-1.13-1.14) - [Installation instructions](https://cert-manager.io/docs/installation/) ##### 📜 Changes since `v1.14.0` ##### Bug or Regression - Fix broken cainjector image value in Helm chart ([#6693](https://redirect.github.com/cert-manager/cert-manager/pull/6693), [@SgtCoDFish](https://redirect.github.com/SgtCoDFish)) - Fix bug in cmctl namespace detection which prevented it being used as a startupapicheck image in namespaces other than cert-manager. ([#6706](https://redirect.github.com/cert-manager/cert-manager/pull/6706), [@inteon](https://redirect.github.com/inteon)) - Fix bug in cmctl which caused `cmctl experimental install` to panic. ([#6706](https://redirect.github.com/cert-manager/cert-manager/pull/6706), [@inteon](https://redirect.github.com/inteon)) ### [`v1.14.0`](https://redirect.github.com/cert-manager/cert-manager/releases/tag/v1.14.0) [Compare Source](https://redirect.github.com/cert-manager/cert-manager/compare/v1.13.6...v1.14.0) cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters. cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions. > ⚠️ This version has known issues. Please install `v1.14.2` instead. ##### ⚠️ Known Issues (please install `v1.14.2`) - ACME Issuer (Let's Encrypt): wrong certificate chain may be used if `preferredChain` is configured: see [release docs](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14/#acme-issuer-lets-encrypt-wrong-certificate-chain-may-be-used-if-preferredchain-is-configured---6755-6757) for more info and mitigations - In cert-manager v1.14.0 and v1.14.1, the `CA` and `SelfSigned` issuers issue certificates with SANs set to non-critical even when the subject is empty. It incorrectly copies the critical field from the CSR. - During the release of `v1.14.0`, the Helm chart for this version was found to use the wrong OCI image for the `cainjector` Deployment, which caused the Helm installation to fail. In order to complete the release, the cert-manager team have manually updated the Helm chart for this version, which contains all the Helm chart fixes which are in `v1.14.1`. - A bug in cmctl namespace detection prevents it being used as a `startupapicheck` image in namespaces other than cert-manager. - A bug in cmctl causes `cmctl experimental install` to panic. ##### 🔧 Breaking Changes The startupapicheck job uses a new OCI image called "startupapicheck", instead of the ctl image. If you run in an environment in which images cannot be pulled, be sure to include the new image. The KeyUsage and BasicConstraints extensions will now be encoded as critical in the CertificateRequest's CSR blob. ##### 🗺️ Major Themes ##### New X.509 Features The cert-manager Certificate resource now allows you to configure a subset of "Other Name" SANs, which are described in the [Subject Alternative Name section of RFC 5280](https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.6) (on page 37). We specifically support any `otherName` type with a `UTF-8` value, such as the [User Principal Name](https://docs.venafi.com/Docs/current/TopNav/Content/Certificates/r-UEP-support-SANs.php) or [`sAMAccountName`](https://learn.microsoft.com/en-us/windows/win32/ad/naming-properties). These are useful when issuing unique certificates for authenticating with LDAP systems such as Microsoft Active Directory. For example you can create certificates with this block in the spec: otherNames: - oid: 1.3.6.1.4.1.311.20.2.3 # UPN OID utf8Value: upn@domain.local The feature is still in alpha stage and requires you to [enable the `OtherName` feature flag in the controller and webhook components](../../installation/configuring-components.md#feature-gates). ##### New CA certificate Features You can now specify the X.509 v3 Authority Information Accessors extension, with URLs for certificates issued by the CA issuer. Users can now use name constraints in CA certificates. To know more details on name constraints check out RFC section https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.10 ##### Security An ongoing security audit of the cert-manager code revealed some weaknesses which we have addressed in this release, such as using more secure default settings in the HTTP servers that serve metrics, healthz and pprof endpoints. This will help mitigate denial-of-service attacks against those important services. All the cert-manager containers are now configured with read only root file system by default, to prevent unexpected changes to the file system of the OCI image. And it is now possible to configure the metrics server to use HTTPS rather than HTTP, so that clients can verify the identity of the metrics server. ##### Other The liveness probe of the cert-manager controller Pod is now enabled by default. There is a new option `.spec.keystores.pkcs12.algorithms` to specify encryption and MAC algorithms for PKCS. ##### 🤝 Community Thanks again to all open-source contributors with commits in this release, including: - [@ABWassim](https://redirect.github.com/ABWassim) - [@JoeNorth](https://redirect.github.com/JoeNorth) - [@allenmunC1](https://redirect.github.com/allenmunC1) - [@asapekia](https://redirect.github.com/asapekia) - [@jeremycampbell](https://redirect.github.com/jeremycampbell) - [@jkroepke](https://redirect.github.com/jkroepke) - [@jsoref](https://redirect.github.com/jsoref) - [@lauraseidler](https://redirect.github.com/lauraseidler) - [@pevidex](https://redirect.github.com/pevidex) - [@phillebaba](https://redirect.github.com/phillebaba) - [@snorwin](https://redirect.github.com/snorwin) - [@tanujd11](https://redirect.github.com/tanujd11) - [@tberreis](https://redirect.github.com/tberreis) - [@vinny](https://redirect.github.com/vinny) Thanks also to the following cert-manager maintainers for their contributions during this release: - [@SgtCoDFish](https://redirect.github.com/SgtCoDFish) - [@SpectralHiss](https://redirect.github.com/SpectralHiss) - [@ThatsMrTalbot](https://redirect.github.com/ThatsMrTalbot) - [@hawksight](https://redirect.github.com/hawksight) - [@inteon](https://redirect.github.com/inteon) - [@maelvls](https://redirect.github.com/maelvls) - [@wallrj](https://redirect.github.com/wallrj) Equally thanks to everyone who provided feedback, helped users and raised issues on GitHub and Slack and joined our meetings! 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://redirect.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 ##### Feature - ACME challenge solver Pod for HTTP01 will get a default annotation of `"cluster-autoscaler.kubernetes.io/safe-to-evict": "true"`. You can provide an annotation of `"cluster-autoscaler.kubernetes.io/safe-to-evict": "false"` in your `podTemplate` if you don't like this. ([#6349](https://redirect.github.com/cert-manager/cert-manager/pull/6349), [@jsoref](https://redirect.github.com/jsoref)) - Added a clock skew detector liveness probe that will force a restart in case we detect a skew between the internal monotonic clock and the system clock of more than 5 minutes. Also, the controller's liveness probe is now enabled by default. ([#6328](https://redirect.github.com/cert-manager/cert-manager/pull/6328), [@inteon](https://redirect.github.com/inteon)) - Added a new flag (--dynamic-serving-leaf-duration) that can adjust the lifetime of the dynamic leaf certificates ([#6552](https://redirect.github.com/cert-manager/cert-manager/pull/6552), [@allenmunC1](https://redirect.github.com/allenmunC1)) - Added support for `otherName` SANS in Certificates ([#6404](https://redirect.github.com/cert-manager/cert-manager/pull/6404), [@SpectralHiss](https://redirect.github.com/SpectralHiss)) - Added the option to specify the X.509 v3 Authority Information Accessors extension CA Issuers URLs for certificates issued by the CA issuer. ([#6486](https://redirect.github.com/cert-manager/cert-manager/pull/6486), [@jeremycampbell](https://redirect.github.com/jeremycampbell-okta)) - Adds cert-manager's new core infrastructure initiative badge! See more details on https://www.bestpractices.dev/projects/8079 ([#6497](https://redirect.github.com/cert-manager/cert-manager/pull/6497), [@SgtCoDFish](https://redirect.github.com/SgtCoDFish)) - All Pods are now configured with `readOnlyRootFilesystem` by default. ([#6453](https://redirect.github.com/cert-manager/cert-manager/pull/6453), [@wallrj](https://redirect.github.com/wallrj)) - MAYBE BREAKING: The startupapicheck job is now handled by an entirely new container called "startupapicheck". This replaces the previous ctl container. If you run in an environment in which images cannot be pulled, be sure to include the new container. ([#6549](https://redirect.github.com/cert-manager/cert-manager/pull/6549), [@SgtCoDFish](https://redirect.github.com/SgtCoDFish)) - New option `.spec.keystores.pkcs12.algorithms` to specify encryption and MAC algorithms for PKCS[#12](https://redirect.github.com/cert-manager/cert-manager/pull/12) keystores. Fixes issues [#5957](https://redirect.github.com/cert-manager/cert-manager/pull/5957) and [#6523](https://redirect.github.com/cert-manager/cert-manager/pull/6523). ([#6548](https://redirect.github.com/cert-manager/cert-manager/pull/6548), [@snorwin](https://redirect.github.com/snorwin)) - The ACME HTTP01 solver Pod is now configured with `readOnlyRootFilesystem: true` ([#6462](https://redirect.github.com/cert-manager/cert-manager/pull/6462), [@wallrj](https://redirect.github.com/wallrj)) - Updates the AWS SDK for Go to 1.48.7 to support Amazon EKS Pod Identity ([#6519](https://redirect.github.com/cert-manager/cert-manager/pull/6519), [@JoeNorth](https://redirect.github.com/JoeNorth)) - Users can now use name constraints in CA certificates. To know more details on name constraints check out RFC section https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.10 ([#6500](https://redirect.github.com/cert-manager/cert-manager/pull/6500), [@tanujd11](https://redirect.github.com/tanujd11)) - ⚠️ potentially breaking ⚠️: The KeyUsage and BasicConstraints extensions will now be encoded as critical in the CertificateRequest's CSR blob. ([#6053](https://redirect.github.com/cert-manager/cert-manager/pull/6053), [@inteon](https://redirect.github.com/inteon)) - Add TLS support to the metrics endpoint through either a certificate file or through dynamically issued certificates ([#6574](https://redirect.github.com/cert-manager/cert-manager/pull/6574), [@ThatsMrTalbot](https://redirect.github.com/ThatsMrTalbot)) - Helm Chart: allow changing the default Deployment `revisionHistoryLimit` ([#6248](https://redirect.github.com/cert-manager/cert-manager/pull/6248), [@tberreis](https://redirect.github.com/tberreis)) - Security: Limit the size of the response body read from HTTP requests by cert-manager. ([#6619](https://redirect.github.com/cert-manager/cert-manager/pull/6619), [@ThatsMrTalbot](https://redirect.github.com/ThatsMrTalbot)) - Support custom `spec.namespaceSelector` for webhooks ([#6638](https://redirect.github.com/cert-manager/cert-manager/pull/6638), [@jkroepke](https://redirect.github.com/jkroepke)) ##### Bug or Regression - BUGFIX\[helm]: Fix issue where webhook feature gates were only set if controller feature gates are set. ([#6380](https://redirect.github.com/cert-manager/cert-manager/pull/6380), [@asapekia](https://redirect.github.com/asapekia)) - Controller ConfigMap is now created only if `.Values.config` is set. ([#6357](https://redirect.github.com/cert-manager/cert-manager/pull/6357), [@ABWassim](https://redirect.github.com/ABWassim)) - Fix runaway bug caused by multiple Certificate resources that point to the same Secret resource. ([#6406](https://redirect.github.com/cert-manager/cert-manager/pull/6406), [@inteon](https://redirect.github.com/inteon)) - Fix(helm): templating of required value in controller and webhook ConfigMap resources ([#6435](https://redirect.github.com/cert-manager/cert-manager/pull/6435), [@ABWassim](https://redirect.github.com/ABWassim)) - Fixed a webhook validation error message when the key algorithm was invalid. ([#6571](https://redirect.github.com/cert-manager/cert-manager/pull/6571), [@pevidex](https://redirect.github.com/pevidex)) - Fixed error messaging when setting up vault issuer ([#6433](https://redirect.github.com/cert-manager/cert-manager/pull/6433), [@vinny](https://redirect.github.com/vinny-sabatini)) - `GHSA-vgf6-pvf4-34rq`: The webhook server now returns HTTP error 413 (Content Too Large) for requests with body size `>= 3MiB`. This is to mitigate DoS attacks that attempt to crash the webhook process by sending large requests that exceed the available memory. The webhook server now returns HTTP error 400 (Bad Request) if the request contains an empty body. The webhook server now returns HTTP error 500 (Internal Server Error) rather than crashing, if the code panics while handling a request. ([#6498](https://redirect.github.com/cert-manager/cert-manager/pull/6498), [@inteon](https://redirect.github.com/inteon)) - Increase the default webhook timeout to its maximum value of 30 seconds, so that the underlying timeout error message has more chance of being returned to the end user. ([#6488](https://redirect.github.com/cert-manager/cert-manager/pull/6488), [@wallrj](https://redirect.github.com/wallrj)) - Listeners that do not support TLS on Gateway resources will now not raise `BadConfig` warnings anymore ([#6347](https://redirect.github.com/cert-manager/cert-manager/pull/6347), [@lauraseidler](https://redirect.github.com/lauraseidler)) - Mitigate potential Slowloris attacks by setting `ReadHeaderTimeout` in all `http.Server` instances ([#6534](https://redirect.github.com/cert-manager/cert-manager/pull/6534), [@wallrj](https://redirect.github.com/wallrj)) - 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.`. ([#6398](https://redirect.github.com/cert-manager/cert-manager/pull/6398), [@maelvls](https://redirect.github.com/maelvls)) - Update experimental install and uninstall commands to have flag parity with the rest of the CLI ([#6562](https://redirect.github.com/cert-manager/cert-manager/pull/6562), [@ThatsMrTalbot](https://redirect.github.com/ThatsMrTalbot)) - Webhook ConfigMap if now created only if `.Values.webhook.config` is set. ([#6360](https://redirect.github.com/cert-manager/cert-manager/pull/6360), [@ABWassim](https://redirect.github.com/ABWassim)) - BUGFIX: Ensure `otherName` SAN changes in Certificate resources trigger re-issuance. ([#6620](https://redirect.github.com/cert-manager/cert-manager/pull/6620), [@SpectralHiss](https://redirect.github.com/SpectralHiss)) - Bugfix: Publish the `startupapicheck` image to `quay.io` ([#6609](https://redirect.github.com/cert-manager/cert-manager/pull/6609), [@wallrj](https://redirect.github.com/wallrj)) ##### Other (Cleanup or Flake) - Cert-manager is now built with Go 1.21.5 ([#6545](https://redirect.github.com/cert-manager/cert-manager/pull/6545), [@wallrj](https://redirect.github.com/wallrj)) - Bump Go to `1.21.3` to address `CVE-2023-39325`. Also bumps base images. ([#6410](https://redirect.github.com/cert-manager/cert-manager/pull/6410), [@SgtCoDFish](https://redirect.github.com/SgtCoDFish)) - Bump `golang.org/x/net v0.15.0 => v0.17.0` as part of addressing `CVE-2023-44487` / `CVE-2023-39325` ([#6427](https://redirect.github.com/cert-manager/cert-manager/pull/6427), [@SgtCoDFish](https://redirect.github.com/SgtCoDFish)) - Check code for unintended use of `crypto/md5`, a weak cryptographic primitive; using `golangci-lint` / `gosec` (G501). ([#6581](https://redirect.github.com/cert-manager/cert-manager/pull/6581), [@wallrj](https://redirect.github.com/wallrj)) - Check code for unintended use of `crypto/sha1`, a weak cryptographic primitive; using `golangci-lint` / `gosec` (G505). ([#6579](https://redirect.github.com/cert-manager/cert-manager/pull/6579), [@wallrj](https://redirect.github.com/wallrj)) - Check code for unintended use of weak random number generator (`math/rand` instead of `crypto/rand`); using `golangci-lint` / `gosec` (G404). ([#6582](https://redirect.github.com/cert-manager/cert-manager/pull/6582), [@wallrj](https://redirect.github.com/wallrj)) - Cleanup: Restrict MutatingWebhookConfiguration to only CertificateRequest resources ([#6311](https://redirect.github.com/cert-manager/cert-manager/pull/6311), [@hawksight](https://redirect.github.com/hawksight)) - Deprecated `pkg/util.RandStringRunes` and `pkg/controller/test.RandStringBytes`. Use `k8s.io/apimachinery/pkg/util/rand.String` instead. ([#6585](https://redirect.github.com/cert-manager/cert-manager/pull/6585), [@wallrj](https://redirect.github.com/wallrj)) - Enabled verbose logging in startupapicheck by default, so that if it fails, users can know exactly what caused the failure. ([#6495](https://redirect.github.com/cert-manager/cert-manager/pull/6495), [@wallrj](https://redirect.github.com/wallrj)) - Fix gosec G601: Implicit memory aliasing of items from a range statement ([#6551](https://redirect.github.com/cert-manager/cert-manager/pull/6551), [@wallrj](https://redirect.github.com/wallrj)) - Fix handling of serial numbers in literal certificate subjects. Previously a serial number could be specified in `subject.serialNumber` while using a literal certificate subject. This was a mistake and has been fixed. ([#6533](https://redirect.github.com/cert-manager/cert-manager/pull/6533), [@inteon](https://redirect.github.com/inteon)) - The end-to-end tests can now test the cert-manager Vault Issuer on an OpenShift cluster. ([#6391](https://redirect.github.com/cert-manager/cert-manager/pull/6391), [@wallrj](https://redirect.github.com/wallrj)) - Update cert-manager's distroless base images from Debian 11 to Debian 12. This should have no practical effects on users. ([#6583](https://redirect.github.com/cert-manager/cert-manager/pull/6583), [@inteon](https://redirect.github.com/inteon)) - Updated all code using GatewayAPI to use the now GA v1 APIs ([#6559](https://redirect.github.com/cert-manager/cert-manager/pull/6559), [@ThatsMrTalbot](https://redirect.github.com/ThatsMrTalbot)) - Upgrade Go from 1.20.7 to 1.20.8. ([#6369](https://redirect.github.com/cert-manager/cert-manager/pull/6369), [@inteon](https://redirect.github.com/inteon)) - Upgrade `github.com/emicklei/go-restful/v3` to `v3.11.0` because `v3.10.2` is labeled as "DO NOT USE". ([#6366](https://redirect.github.com/cert-manager/cert-manager/pull/6366), [@inteon](https://redirect.github.com/inteon)) - Use the new generic `sets.Set` type in place of the deprecated `sets.String`. ([#6586](https://redirect.github.com/cert-manager/cert-manager/pull/6586), [@wallrj](https://redirect.github.com/wallrj)) - cert-manager is now built with Go `v1.21.6` ([#6628](https://redirect.github.com/cert-manager/cert-manager/pull/6628), [@SgtCoDFish](https://redirect.github.com/SgtCoDFish)) - Update the Azure SDK and remove deprecated `autorest` dependency ([#5452](https://redirect.github.com/cert-manager/cert-manager/pull/5452), [@phillebaba](https://redirect.github.com/phillebaba)) - The cert-manager E2E tests can now be run on Kubernetes 1.29 ([#6641](https://redirect.github.com/cert-manager/cert-manager/pull/6641), [@wallrj](https://redirect.github.com/wallrj))Configuration
📅 Schedule: Branch creation - "every weekend" in timezone America/New_York, 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 Renovate Bot.