Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update module github.com/cert-manager/cert-manager to v1.16.2 #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update module github.com/cert-manager/cert-manager to v1.16.2 #11

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 13, 2022 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/cert-manager/cert-manager v1.8.1 -> v1.16.2 age adoption passing confidence

Release Notes

cert-manager/cert-manager (github.com/cert-manager/cert-manager)

v1.16.2

Compare Source

v1.16.1

Compare Source

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

The cert-manager 1.16 release includes: new Helm chart features, more Prometheus metrics, memory optimizations, and various improvements and bug fixes for the ACME issuer and Venafi Issuer.

📖 Read the complete 1.16 release notes before upgrading.

📜Changes since v1.16.0

Bug or Regression
  • BUGFIX: Helm schema validation: the new schema validation was too strict for the "global" section. Since the global section is shared across all charts and sub-charts, we must also allow unknown fields. (#​7348, @inteon)
  • BUGFIX: Helm will now accept percentages for the podDisruptionBudget.minAvailable and podDisruptionBudget.maxAvailable values. (#​7345, @inteon)
  • Helm: allow enabled to be set as a value to toggle cert-manager as a dependency. (#​7356, @inteon)
  • BUGFIX: A change in v1.16.0 caused cert-manager's ACME ClusterIssuer to look in the wrong namespace for resources required for the issuance (e.g. credential Secrets). This is now fixed in v1.16.1. (#​7342, @inteon)

v1.16.0

Compare Source

v1.15.4

Compare Source

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

This patch release of cert-manager 1.15 makes several changes to how PEM input is validated, adding maximum sizes appropriate to the type of PEM data which is being parsed.

This is to prevent an unacceptable slow-down in parsing specially crafted PEM data. The issue was found by Google's OSS-Fuzz project.

The issue is low severity; to exploit the PEM issue would require privileged access which would likely allow Denial-of-Service through other methods.

In addition, since most PEM data parsed by cert-manager comes from ConfigMap or Secret resources which have
a max size limit of approximately 1MB, it's difficult to force cert-manager to parse large amounts of PEM data.

Further information will be published in a security advisory when all supported cert-manager releases have been patched.

In addition, the version of Go used to build cert-manager 1.15 was updated along with the base images, and a Route53 bug fix was backported.

Changes by Kind

Bug or Regression
  • Bugfix: Prevent aggressive Route53 retries caused by STS authentication failures by removing the Amazon Request ID from STS errors. (#​7261, @​cert-manager-bot)
  • Set a maximum size for PEM inputs which cert-manager will accept to remove possibility of taking a long time to process an input (#​7402, @​SgtCoDFish)
Other (Cleanup or Flake)

v1.15.3

Compare Source

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

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.2
Bug or Regression
  • BUGFIX: the dynamic certificate source used by the webhook TLS server failed to detect a root CA approaching expiration, due to a calculation error. This will cause the webhook TLS server to fail renewing its CA certificate. Please upgrade before the expiration of this CA certificate is reached. (#​7232, @​cert-manager-bot)

v1.15.2

Compare Source

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

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.1
Bug or Regression

v1.15.1

Compare Source

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

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.0

Bug or Regression
  • BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#​7111, @​inteon)
Other (Cleanup or Flake)

v1.15.0

Compare Source

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

cert-manager 1.15 promotes several features to beta, including GatewayAPI support (ExperimentalGatewayAPISupport), the ability to provide a subject in the Certificate that will be used literally in the CertificateSigningRequest (LiteralCertificateSubject) and the outputting of additional certificate formats (AdditionalCertificateOutputFormats).

[!NOTE]

The cmctl binary have been moved to https://github.com/cert-manager/cmctl/releases.
For the startupapicheck Job you should update references to point at quay.io/jetstack/cert-manager-startupapicheck

[!NOTE]

From this release, the Helm chart will no longer uninstall the CRDs when the chart is uninstalled. If you want the CRDs to be removed on uninstall use crds.keep=false when installing the Helm chart.

Community

Thanks again to all open-source contributors with commits in this release, including: @​Pionerd, @​SgtCoDFish, @​ThatsMrTalbot, @​andrey-dubnik, @​bwaldrep, @​eplightning, @​erikgb, @​findnature, @​gplessis, @​import-shiburin, @​inteon, @​jkroepke, @​lunarwhite, @​mangeshhambarde, @​pwhitehead-splunk & @​rodrigorfk, @​wallrj.

Thanks also to the following cert-manager maintainers for their contributions during this release: @​SgtCoDFish, @​SpectralHiss, @​ThatsMrTalbot, @​hawksight, @​inteon, @​maelvls & @​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, 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 by Kind
Feature
  • GatewayAPI support has graduated to Beta. Add the --enable-gateway-api flag to enable the integration. (#​6961, @​ThatsMrTalbot)
  • Add support to specify a custom key alias in a JKS Keystore (#​6807, @​bwaldrep)
  • Add the ability to communicate with Vault via mTLS when strict client certificates is enabled at Vault server side (#​6614, @​rodrigorfk)
  • Added option to provide additional audiences in the service account auth section for vault (#​6718, @​andrey-dubnik)
  • Venafi Issuer now sends a cert-manager HTTP User-Agent header in all Venafi Rest API requests.
    For example: cert-manager-certificaterequests-issuer-venafi/v1.15.0+(linux/amd64)+cert-manager/ef068a59008f6ed919b98a7177921ddc9e297200. (#​6865, @​wallrj)
  • Add hint to validation error message to help users of external issuers more easily fix the issue if they specify a Kind but forget the Group (#​6913, @​SgtCoDFish)
  • Add support for numeric OID types in LiteralSubject. Eg. "1.2.3.4=String Value" (#​6775, @​inteon)
  • Promote the LiteralCertificateSubject feature to Beta. (#​7030, @​inteon)
  • Promoted the AdditionalCertificateOutputFormats feature gate to Beta (enabled by default). (#​6970, @​erikgb)
  • The Helm chart now allows you to supply extraObjects; a list of yaml manifests which will helm will install and uninstall with the cert-manager manifests. (#​6424, @​gplessis)
  • Update the Route53 provider to support fetching credentials using AssumeRoleWithWebIdentity (#​6878, @​pwhitehead-splunk)
  • Helm can now add optional hostAliases to cert-manager Pod to allow the DNS self-check to pass in custom scenarios. (#​6456, @​Pionerd)
  • Added a new Ingress annotation for copying specific Ingress annotations to Certificate's secretTemplate (#​6839, @​mangeshhambarde)
  • Added option to define additional token audiences for the Vault Kubernetes auth (#​6744, @​andrey-dubnik)
  • Allow cert-manager.io/allow-direct-injection in annotations (#​6801, @​jkroepke)
Design
Bug or Regression
  • BUGFIX: Fixes issue with JSON-logging, where only a subset of the log messages were output as JSON. (#​6779, @​inteon)
  • BUGFIX: JKS and PKCS12 stores now contain the full set of CAs specified by an issuer (#​6806, @​bwaldrep)
  • BUGFIX: cainjector leaderelection flag/config option defaults are missing (#​6816, @​inteon)
  • BUGFIX: cert-manager issuers incorrectly copied the critical flag from the CSR instead of re-calculating that field themselves. (#​6724, @​inteon)
  • Breaking Change: Fixed unintended certificate chain is used if preferredChain is configured. (#​6755, @​import-shiburin)
  • Bugfix: LiteralSubjects with a #= value can result in memory issues due to faulty BER parser (github.com/go-asn1-ber/asn1-ber). (#​6770, @​inteon)
  • DigitalOcean: Ensure that only TXT records are considered for deletion when cleaning up after an ACME challenge (#​6875, @​SgtCoDFish)
  • Fix backwards incompatible removal of default prometheus Service resource. (#​6699, @​inteon)
  • Fix broken cainjector image value in Helm chart (#​6692, @​SgtCoDFish)
  • Helm: Fix a bug in the logic that differentiates between 0 and an empty value. (#​6713, @​inteon)
  • Make sure the Azure SDK error messages are stable. (#​6676, @​inteon)
  • When using the literalSubject on a Certificate, the webhook validation for the common name now also points to the literalSubject. (#​6767, @​lunarwhite)
  • Bump golang.org/x/net to fix CVE-2023-45288 (#​6929, @​SgtCoDFish)
  • Fix ACME issuer being stuck waiting for DNS propagation when using Azure DNS with multiple instances issuing for the same FQDN (#​6351, @​eplightning)
  • Fix cainjector ConfigMap not mounted in the cainjector deployment. (#​7055, @​inteon)
  • Added disableAutoApproval and approveSignerNames Helm chart options. (#​7054, @​inteon)
Other (Cleanup or Flake)

v1.14.7

Compare Source

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

📜 Changes since v1.14.6
Bugfixes
Other (Cleanup or Flake)

v1.14.6

Compare Source

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

📜 Changes since v1.14.5
Other (Cleanup or Flake)

v1.14.5

Compare Source

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 for reporting this issue and testing the fix!

It also patches CVE-2023-45288.

📜 Changes since v1.14.4

  • ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see 1.14 release notes for more information.

Changes

Bug or Regression

v1.14.4

Compare Source

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 for more info and mitigations
ℹ️ Documentation

Release notes
Upgrade notes
Installation instructions

🔧 Breaking changes

See Breaking changes in v1.14.0 release notes

📜 Changes since v1.14.3
Bug or Regression
Other (Cleanup or Flake)

v1.14.3

Compare Source

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
ℹ️ Documentation

Release notes
Upgrade notes
Installation instructions

🔧 Breaking changes

See Breaking changes in v1.14.0 release notes

📜 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, @​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, @​jetstack-bot)

v1.14.2

Compare Source

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
ℹ️ Documentation

Release notes
Upgrade notes
Installation instructions

🔧 Breaking changes

See Breaking changes in v1.14.0 release notes

📜 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, @​jetstack-bot)
  • Helm: Fix a bug in the logic that differentiates between 0 and an empty value. (#​6729, @​jetstack-bot)
Other (Cleanup or Flake)

v1.14.1

Compare Source

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 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

ℹ️ Documentation
📜 Changes since v1.14.0
Bug or Regression
  • Fix broken cainjector image value in Helm chart (#​6693, @​SgtCoDFish)
  • Fix bug in cmctl namespace detection which prevented it being used as a startupapicheck image in namespaces other than cert-manager. (#​6706, @​inteon)
  • Fix bug in cmctl which caused cmctl experimental install to panic. (#​6706, @​inteon)

v1.14.0

Compare Source

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 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 (on page 37).

We specifically support any otherName type with a UTF-8 value, such as the User Principal Name or sAMAccountName.
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: [email protected]

The feature is still in alpha stage and requires you to enable the OtherName feature flag in the controller and webhook components.

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:

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 and joined our meetings!

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
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, @​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, @​inteon)
  • Added a new flag (--dynamic-serving-leaf-duration) that can adjust the lifetime of the dynamic leaf certificates (#​6552, @​allenmunC1)
  • Added support for otherName SANS in Certificates (#​6404, @​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, @​jeremycampbell)
  • Adds cert-manager's new core infrastructure initiative badge! See more details on https://www.bestpractices.dev/projects/8079 (#​6497, @​SgtCoDFish)
  • All Pods are now configured with readOnlyRootFilesystem by default. (#​6453, @​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, @​SgtCoDFish)
  • New option .spec.keystores.pkcs12.algorithms to specify encryption and MAC algorithms for PKCS#​12 keystores. Fixes issues #​5957 and #​6523. (#​6548, @​snorwin)
  • The ACME HTTP01 solver Pod is now configured with readOnlyRootFilesystem: true (#​6462, @​wallrj)
  • Updates the AWS SDK for Go to 1.48.7 to support Amazon EKS Pod Identity (#​6519, @​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, @​tanujd11)
  • ⚠️ potentially breaking ⚠️: The KeyUsage and BasicConstraints extensions will now be encoded as critical in the CertificateRequest's CSR blob. (#​6053, @​inteon)
  • Add TLS support to the metrics endpoint through either a certificate file or through dynamically issued certificates (#​6574, @​ThatsMrTalbot)
  • Helm Chart: allow changing the default Deployment revisionHistoryLimit (#​6248, @​tberreis)
  • Security: Limit the size of the response body read from HTTP requests by cert-manager. (#​6619, @​ThatsMrTalbot)
  • Support custom spec.namespaceSelector for webhooks (#​6638, @​jkroepke)
Bug or Regression
  • BUGFIX[helm]: Fix issue where webhook feature gates were only set if controller feature gates are set. (#​6380, @​asapekia)
  • Controller ConfigMap is now created only if .Values.config is set. (#​6357, @​ABWassim)
  • Fix runaway bug caused by multiple Certificate resources that point to the same Secret resource. (#​6406, @​inteon)
  • Fix(helm): templating of required value in controller and webhook ConfigMap resources (#​6435, @​ABWassim)
  • Fixed a webhook validation error message when the key algorithm was invalid. (#​6571, @​pevidex)
  • Fixed error messaging when setting up vault issuer (#​6433, @​vinny)
  • 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, @​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, @​wallrj)
  • Listeners that do not support TLS on Gateway resources will now not raise BadConfig warnings anymore (#​6347, @​lauraseidler)
  • Mitigate potential Slowloris attacks by setting ReadHeaderTimeout in all http.Server instances (#​6534, @​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, @​maelvls)
  • Update experimental install and uninstall commands to have flag parity with the rest of the CLI (#​6562, @​ThatsMrTalbot)
  • Webhook ConfigMap if now created only if .Values.webhook.config is set. (#​6360, @​ABWassim)
  • BUGFIX: Ensure otherName SAN changes in Certificate resources trigger re-issuance. (#​6620, @​SpectralHiss)
  • Bugfix: Publish the startupapicheck image to quay.io (#​6609, @​wallrj)
Other (Cleanup or Flake)
  • Cert-manager is now built with Go 1.21.5 (#​6545, @​wallrj)
  • Bump Go to 1.21.3 to address CVE-2023-39325. Also bumps base images. (#​6410, @​SgtCoDFish)
  • Bump golang.org/x/net v0.15.0 => v0.17.0 as part of addressing CVE-2023-44487 / CVE-2023-39325 (#​6427, @​SgtCoDFish)
  • Check code for unintended use of crypto/md5, a weak cryptographic primitive; using golangci-lint / gosec (G501). (#​6581, @​wallrj)
  • Check code for unintended use of crypto/sha1, a weak cryptographic primitive; using golangci-lint / gosec (G505). (#​6579, @​wallrj)
  • Check code for unintended use of weak random number generator (math/rand instead of crypto/rand); using golangci-lint / gosec (G404). (#​6582, @​wallrj)
  • Cleanup: Restrict MutatingWebhookConfiguration to only CertificateRequest resources (#​6311, @​hawksight)
  • Deprecated pkg/util.RandStringRunes and pkg/controller/test.RandStringBytes. Use k8s.io/apimachinery/pkg/util/rand.String instead. (#​6585, @​wallrj)
  • Enabled verbose logging in startupapicheck by default, so that if it fails, users can know exactly what caused the failure. (#​6495, @​wallrj)
  • Fix gosec G601: Implicit memory aliasing of items from a range statement (#​6551, @​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, @​inteon)
  • The end-to-end tests can now test the cert-manager Vault Issuer on an OpenShift cluster. (#​6391, @​wallrj)
  • Update cert-manager's distroless base images from Debian 11 to Debian 12. This should have no practical effects on users. (#​6583, @​inteon)
  • Updated all code using GatewayAPI to use the now GA v1 APIs (#​6559, @​ThatsMrTalbot)
  • Upgrade Go from 1.20.7 to 1.20.8. (#​6369, @​inteon)
  • Upgrade github.com/emicklei/go-restful/v3 to v3.11.0 because v3.10.2 is labeled as "DO NOT USE". (#​6366, @​inteon)
  • Use the new generic sets.Set type in place of the deprecated sets.String. (#​6586, @​wallrj)
  • cert-manager is now built with Go v1.21.6 (#​6628, @​SgtCoDFish)
  • Update the Azure SDK and remove deprecated autorest dependency (#​5452, @​phillebaba)
  • The cert-manager E2E tests can now be run on Kubernetes 1.29 (#​6641, @​wallrj)

v1.13.6

Compare Source

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

v1.13.6 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 for reporting this issue and testing the fix!

It also patches CVE-2023-45288.

Known Issues

  • ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see 1.14 release notes for more information.

Changes

Bug or Regression

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependency label Oct 13, 2022
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch 2 times, most recently from d2ed739 to 86f8452 Compare October 17, 2022 15:56
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.9.1 Update module github.com/cert-manager/cert-manager to v1.10.0 Oct 17, 2022
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.10.0 Update module github.com/cert-manager/cert-manager to v1.10.0 - autoclosed Nov 17, 2022
@renovate renovate bot closed this Nov 17, 2022
@renovate renovate bot deleted the renovate/github.com-cert-manager-cert-manager-1.x branch November 17, 2022 15:28
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.10.0 - autoclosed Update module github.com/cert-manager/cert-manager to v1.10.0 Nov 17, 2022
@renovate renovate bot restored the renovate/github.com-cert-manager-cert-manager-1.x branch November 17, 2022 18:28
@renovate renovate bot reopened this Nov 17, 2022
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 86f8452 to 6f8368a Compare November 18, 2022 18:34
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.10.0 Update module github.com/cert-manager/cert-manager to v1.10.1 Nov 18, 2022
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.10.1 Update module github.com/cert-manager/cert-manager to v1.10.1 - autoclosed Dec 10, 2022
@renovate renovate bot closed this Dec 10, 2022
@renovate renovate bot deleted the renovate/github.com-cert-manager-cert-manager-1.x branch December 10, 2022 02:05
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.10.1 - autoclosed Update module github.com/cert-manager/cert-manager to v1.10.1 Dec 10, 2022
@renovate renovate bot restored the renovate/github.com-cert-manager-cert-manager-1.x branch December 10, 2022 04:18
@renovate renovate bot reopened this Dec 10, 2022
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 6f8368a to 81d966d Compare March 16, 2023 06:34
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.10.1 Update module github.com/cert-manager/cert-manager to v1.11.0 Mar 16, 2023
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 81d966d to 14a93fe Compare April 17, 2023 12:27
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.11.0 Update module github.com/cert-manager/cert-manager to v1.11.1 Apr 17, 2023
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.11.1 Update module github.com/cert-manager/cert-manager to v1.12.1 May 28, 2023
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 14a93fe to 8c4e23d Compare May 28, 2023 10:05
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 8c4e23d to 93b20b0 Compare June 16, 2023 15:01
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.12.1 Update module github.com/cert-manager/cert-manager to v1.12.2 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 93b20b0 to e03f80c Compare July 26, 2023 13:54
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.12.2 Update module github.com/cert-manager/cert-manager to v1.12.3 Jul 26, 2023
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from e03f80c to a843fd1 Compare September 1, 2023 18:50
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.12.3 Update module github.com/cert-manager/cert-manager to v1.12.4 Sep 1, 2023
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.14.0 Update module github.com/cert-manager/cert-manager to v1.14.1 Feb 2, 2024
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 532a3da to 36d7139 Compare February 8, 2024 12:53
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.14.1 Update module github.com/cert-manager/cert-manager to v1.14.2 Feb 8, 2024
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 36d7139 to 3db8609 Compare February 23, 2024 09:14
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.14.2 Update module github.com/cert-manager/cert-manager to v1.14.3 Feb 23, 2024
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 3db8609 to 5c6f55d Compare March 8, 2024 13:29
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.14.3 Update module github.com/cert-manager/cert-manager to v1.14.4 Mar 8, 2024
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 5c6f55d to 1904bf8 Compare April 14, 2024 10:31
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 1904bf8 to 395c857 Compare April 25, 2024 14:22
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.14.4 Update module github.com/cert-manager/cert-manager to v1.14.5 Apr 25, 2024
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 395c857 to 24d59e4 Compare May 9, 2024 10:57
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jun 4, 2024 •
edited
Loading

ℹ Artifact update notice

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):

  • 45 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.17 -> 1.23.3
github.com/go-logr/logr v1.2.3 -> v1.4.2
github.com/stretchr/testify v1.8.0 -> v1.9.0
k8s.io/api v0.23.5 -> v0.31.1
k8s.io/apiextensions-apiserver v0.23.5 -> v0.31.1
k8s.io/apimachinery v0.23.5 -> v0.31.1
k8s.io/client-go v0.23.5 -> v0.31.1
sigs.k8s.io/controller-runtime v0.11.2 -> v0.19.0
sigs.k8s.io/controller-tools v0.7.0 -> v0.15.0
github.com/beorn7/perks v1.0.1 -> v1.0.1
github.com/cespare/xxhash/v2 v2.1.2 -> v2.3.0
github.com/davecgh/go-spew v1.1.1 -> v1.1.2-0.20180830191138-d8f796af33cc
github.com/fatih/color v1.13.0 -> v1.16.0
github.com/fsnotify/fsnotify v1.5.1 -> v1.7.0
github.com/golang/protobuf v1.5.2 -> v1.5.4
github.com/google/go-cmp v0.5.6 -> v0.6.0
github.com/google/uuid v1.3.0 -> v1.6.0
github.com/imdario/mergo v0.3.12 -> v0.3.16
github.com/inconshreveable/mousetrap v1.0.0 -> v1.1.0
github.com/mattn/go-colorable v0.1.12 -> v0.1.13
github.com/mattn/go-isatty v0.0.14 -> v0.0.20
github.com/pmezard/go-difflib v1.0.0 -> v1.0.1-0.20181226105442-5d4384ee4fb2
github.com/prometheus/client_golang v1.11.0 -> v1.20.4
github.com/prometheus/client_model v0.2.0 -> v0.6.1
github.com/prometheus/common v0.28.0 -> v0.55.0
github.com/prometheus/procfs v0.6.0 -> v0.15.1
github.com/spf13/cobra v1.3.0 -> v1.8.1
go.uber.org/multierr v1.6.0 -> v1.11.0
go.uber.org/zap v1.19.1 -> v1.27.0
golang.org/x/mod v0.5.0 -> v0.20.0
golang.org/x/net v0.0.0-20220107192237-5cfca573fb4d -> v0.29.0
golang.org/x/oauth2 v0.0.0-20211104180415-d3ed0bb246c8 -> v0.23.0
golang.org/x/sys v0.0.0-20211216021012-1d35b9e2eb4e -> v0.25.0
golang.org/x/term v0.0.0-20210927222741-03fcf44c2211 -> v0.24.0
golang.org/x/text v0.3.7 -> v0.18.0
golang.org/x/time v0.0.0-20210723032227-1f47c861a9ac -> v0.6.0
golang.org/x/tools v0.1.6-0.20210820212750-d4cc65f0b2ff -> v0.24.0
gomodules.xyz/jsonpatch/v2 v2.2.0 -> v2.4.0
google.golang.org/protobuf v1.27.1 -> v1.34.2
k8s.io/klog/v2 v2.30.0 -> v2.130.1
k8s.io/kube-openapi v0.0.0-20211115234752-e816edb12b65 -> v0.0.0-20240903163716-9e1beecbcb38
k8s.io/utils v0.0.0-20211116205334-6203023598ed -> v0.0.0-20240921022957-49e7df575cb6
sigs.k8s.io/gateway-api v0.4.1 -> v1.1.0
sigs.k8s.io/json v0.0.0-20211020170558-c049b76a60c6 -> v0.0.0-20221116044647-bc3834ca7abd
sigs.k8s.io/structured-merge-diff/v4 v4.2.1 -> v4.4.1
sigs.k8s.io/yaml v1.3.0 -> v1.4.0

@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 24d59e4 to a50ba48 Compare June 5, 2024 15:38
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.14.5 Update module github.com/cert-manager/cert-manager to v1.15.0 Jun 5, 2024
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from a50ba48 to 1efb073 Compare June 26, 2024 19:57
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.15.0 Update module github.com/cert-manager/cert-manager to v1.15.1 Jun 26, 2024
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 1efb073 to 0f4a442 Compare July 14, 2024 08:48
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 0f4a442 to 4ba6078 Compare July 30, 2024 13:45
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.15.1 Update module github.com/cert-manager/cert-manager to v1.15.2 Jul 30, 2024
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 4ba6078 to 3750b2b Compare August 16, 2024 11:32
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.15.2 Update module github.com/cert-manager/cert-manager to v1.15.3 Aug 16, 2024
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 3750b2b to 4db76c6 Compare September 11, 2024 14:54
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 4db76c6 to 6722797 Compare October 3, 2024 13:41
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.15.3 Update module github.com/cert-manager/cert-manager to v1.16.0 Oct 3, 2024
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 6722797 to 513b093 Compare October 9, 2024 13:49
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.16.0 Update module github.com/cert-manager/cert-manager to v1.16.1 Oct 9, 2024
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 513b093 to 8dcfc8c Compare November 17, 2024 15:39
@renovate
Update module github.com/cert-manager/cert-manager to v1.16.2
20b70e8 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/github.com-cert-manager-cert-manager-1.x branch from 8dcfc8c to 20b70e8 Compare November 20, 2024 18:23
@renovate renovate bot changed the title Update module github.com/cert-manager/cert-manager to v1.16.1 Update module github.com/cert-manager/cert-manager to v1.16.2 Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependency
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants