Release 1.14

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.

📢 The cert-manager CLI is moving to a new GitHub repository

After this release, cmctl will no longer be released with cert-manager itself, and there will no further quay.io/jetstack/cert-manager-ctl OCI images.

Read The cert-manager Command Line Tool (cmctl) page to learn more.

Known Issues

ACME Issuer (Let's Encrypt): wrong certificate chain may be used if `preferredChain` is configured - #6755, #6757

On Thursday, Feb 8th, 2024, Let's Encrypt stopped providing their cross-signed certificate chain by default, in requests made to their /acme/certificate API endpoint. Instead the short-chain is returned by default and the long-chain (cross-signed) certificate chain is now included among the "alternate" chains. The cert-manager ACME Issuer API has a preferredChain field since v1.0.0, which is documented as follows:

PreferredChain is the chain to use if the ACME server outputs multiple. PreferredChain is no guarantee that this one gets delivered by the ACME endpoint. For example, for Let’s Encrypt’s DST cross sign you would use: “DST Root CA X3” or “ISRG Root X1” for the newer Let’s Encrypt root CA. This value picks the first certificate bundle in the ACME alternative chains that has a certificate with this value as its issuer’s CN.

The problem is that the preferredChain feature matches the issuer CN of any certificate in the chain. The result is that: Some users who set Isser.spec.acme.preferredChain: ISRG Root X1 in order to get early access to the Let's Encrypt short-chain certificates, will get long-chain (cross-signed) certificates when they renew after February 8th, 2024. But most users will not be affected. Their new certificates will contain the short-chain (not cross-signed) which terminates at ISRG Root X1.

The cert-manager maintainers are considering how to address this problem for the next release (1.15), without breaking users who have come to rely on the existing, documented behavior.

🔖 Read cert-manager PR 6755 (bugfix: wrong certificate chain is used if preferredChain is configured) to learn about the bug and to see the proposed fix.

🔖 Read Let’s Encrypt: chain of trust to learn about the hierarchy of root and intermediate certificates.

Workarounds

You can remove the spec.acme.preferredChainChain: ISRG Root X1 field from the Issuer or ClusterIssuer. And then renew any certificates which use that issuer and which have been renewed since Feb 8th, 2024. The new certificates will have a shorter chain which terminates at the self-signed root certificate for ISRG Root X1.
You can do nothing. The affected certificates will have a longer chain which terminates at DST Root CA X3 and which contains the cross-signed intermediate certificate for ISRG Root X1, which expires on September 30th, 2024. But that's OK as long as DST Root CA X3 is trusted by your clients. And your 90 day leaf certificate is certain to be be renewed before that date, and certain to be renewed after June 6th, 2024, on which day Let's Encrypt will stop providing the longer cross-signed chain entirely.

⚠️ There may be clients that are incompatible with DST Root CA X3.

`v1.14.7`

Bugfixes

BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#7114, @cert-manager-bot)

Other (Cleanup or Flake)

Upgrade go-jose library to fix CVE-2024-28180 trivy alert. (#7109, @inteon)
Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to address CVE-2024-35255 (#7099, @ThatsMrTalbot)

`v1.14.6`

Changes by Kind

Other (Cleanup or Flake)

Upgrade Go to 1.21.10, fixing GO-2024-2824 (https://github.com/advisories/GHSA-2jwv-jmq4-4j3r). (#7008, @inteon)
Helm BUGFIX: the cainjector ConfigMap was not mounted in the cainjector deployment. (#7053, @cert-manager-bot)
Updated Go to 1.21.11 bringing in security fixes for archive/zip and net/netip. (#7076, @ThatsMrTalbot)

`v1.14.5`

Special thanks to @BobyMCbobs for reporting and testing the DigitalOcean issue!

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

DigitalOcean: Ensure that only TXT records are considered for deletion when cleaning up after an ACME challenge (#6893, @SgtCoDFish)
Bump golang.org/x/net to address CVE-2023-45288 (#6931, @SgtCoDFish)

`v1.14.4`

📢 When upgrading to cert-manager release 1.14, please skip v1.14.0, v1.14.1, v1.14.2 and v1.14.3 and install this patch version instead.

Changes since `v1.14.3`

Bug or Regression

Allow cert-manager.io/allow-direct-injection in annotations (#6809, @jetstack-bot)
BUGFIX: JKS and PKCS12 stores now contain the full set of CAs specified by an issuer (#6812, @jetstack-bot)
BUGFIX: cainjector leader election flag/ config option defaults are missing (#6819, @jetstack-bot)

Other (Cleanup or Flake)

Bump base images. (#6842, @inteon)
Upgrade Helm: fix CVE-2024-26147 alert (#6834, @inteon)
Upgrade go to 1.21.8: fixes CVE-2024-24783 (#6825, @jetstack-bot)
Upgrade google.golang.org/protobuf: fixing GO-2024-2611 (#6829, @inteon)

`v1.14.3`

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`

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)

Bump Go to 1.21.7 (#6735, @jetstack-bot)

`v1.14.1`

cert-manager v1.14.1 fixes bugs found during the release of v1.14.0.

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`

⚠️ This version has known issues.

During the release of v1.14.0, the Helm chart was found to use the wrong OCI image for the cainjector Deployment, which caused the Helm installation and the static manifest based installation to fail. Upon discovery of this bug, the release of v1.14.0 was paused before the Helm chart or GitHub release were published; but the Git tag and the OCI images had already been published.

The cert-manager team next fixed the Helm chart and two other bugs which are listed in the "Known Issues" section below, and then released v1.14.1, which is the version that users are strongly advised to install when they upgrade to 1.14.

In order to complete the stalled v1.14.0 release, the Helm chart and static YAML installation files were regenerated on a team member's laptop, using exactly the same build scripts as are used in the automated release process, and using the v1.14.1 version of the code. The working v1.14.0 Helm chart was published, and the working versions of the static manifest files attached to the draft v1.14.0 GitHub release, and that was then published.

For these reasons, users are strongly advised to skip this version and install the latest patch Helm chart instead.

Known Issues

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. But users are strongly advised to skip this version and install the v1.14.1 Helm chart instead.
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: upn@domain.local

The feature is still in alpha stage and requires you to enable the OtherNames 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, using the new issuingCertificateURLs field.

Users can now use name constraints in CA certificates. To know more details on name constraints check out RFC5280 section 4.2.1.10.

Security

An ongoing CNCF 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.profile to specify encryption and HMAC algorithms for PKCS keystores. See the API reference for configuration options.

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)

Dependencies

Added

cloud.google.com/go/cloudsqlconn: v1.4.3
github.com/Azure/azure-sdk-for-go/sdk/azcore: v1.9.1
github.com/Azure/azure-sdk-for-go/sdk/azidentity: v1.4.0
github.com/Azure/azure-sdk-for-go/sdk/internal: v1.5.1
github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/dns/armdns: v1.2.0
github.com/AzureAD/microsoft-authentication-library-for-go: v1.1.1
github.com/Masterminds/goutils: v1.1.1
github.com/Masterminds/semver/v3: v3.1.1
github.com/Masterminds/sprig/v3: v3.2.1
github.com/Venafi/vcert/v5: v5.3.0
github.com/dnaeon/go-vcr: v1.2.0
github.com/golang-jwt/jwt/v5: v5.0.0
github.com/hashicorp/go-secure-stdlib/plugincontainer: v0.2.2
github.com/huandu/xstrings: v1.3.2
github.com/jackc/chunkreader/v2: v2.0.1
github.com/jackc/pgconn: v1.14.0
github.com/jackc/pgio: v1.0.0
github.com/jackc/pgpassfile: v1.0.0
github.com/jackc/pgproto3/v2: v2.3.2
github.com/jackc/pgservicefile: 091c0ba
github.com/jackc/pgtype: v1.14.0
github.com/jackc/pgx/v4: v4.18.1
github.com/kylelemons/godebug: v1.1.0
github.com/matttproud/golang_protobuf_extensions/v2: v2.0.0
github.com/montanaflynn/stats: v0.7.0
github.com/pkg/browser: 681adbf
github.com/shopspring/decimal: v1.2.0
github.com/sosodev/duration: v1.2.0
github.com/xrash/smetrics: 039620a

Changed

cloud.google.com/go/accessapproval: v1.7.1 → v1.7.4
cloud.google.com/go/accesscontextmanager: v1.8.1 → v1.8.4
cloud.google.com/go/aiplatform: v1.48.0 → v1.58.0
cloud.google.com/go/analytics: v0.21.3 → v0.21.6
cloud.google.com/go/apigateway: v1.6.1 → v1.6.4
cloud.google.com/go/apigeeconnect: v1.6.1 → v1.6.4
cloud.google.com/go/apigeeregistry: v0.7.1 → v0.8.2
cloud.google.com/go/appengine: v1.8.1 → v1.8.4
cloud.google.com/go/area120: v0.8.1 → v0.8.4
cloud.google.com/go/artifactregistry: v1.14.1 → v1.14.6
cloud.google.com/go/asset: v1.14.1 → v1.16.0
cloud.google.com/go/assuredworkloads: v1.11.1 → v1.11.4
cloud.google.com/go/automl: v1.13.1 → v1.13.4
cloud.google.com/go/baremetalsolution: v1.1.1 → v1.2.3
cloud.google.com/go/batch: v1.3.1 → v1.7.0
cloud.google.com/go/beyondcorp: v1.0.0 → v1.0.3
cloud.google.com/go/bigquery: v1.53.0 → v1.57.1
cloud.google.com/go/billing: v1.16.0 → v1.18.0
cloud.google.com/go/binaryauthorization: v1.6.1 → v1.8.0
cloud.google.com/go/certificatemanager: v1.7.1 → v1.7.4
cloud.google.com/go/channel: v1.16.0 → v1.17.3
cloud.google.com/go/cloudbuild: v1.13.0 → v1.15.0
cloud.google.com/go/clouddms: v1.6.1 → v1.7.3
cloud.google.com/go/cloudtasks: v1.12.1 → v1.12.4
cloud.google.com/go/compute: v1.23.0 → v1.23.3
cloud.google.com/go/contactcenterinsights: v1.10.0 → v1.12.1
cloud.google.com/go/container: v1.24.0 → v1.29.0
cloud.google.com/go/containeranalysis: v0.10.1 → v0.11.3
cloud.google.com/go/datacatalog: v1.16.0 → v1.19.0
cloud.google.com/go/dataflow: v0.9.1 → v0.9.4
cloud.google.com/go/dataform: v0.8.1 → v0.9.1
cloud.google.com/go/datafusion: v1.7.1 → v1.7.4
cloud.google.com/go/datalabeling: v0.8.1 → v0.8.4
cloud.google.com/go/dataplex: v1.9.0 → v1.13.0
cloud.google.com/go/dataproc/v2: v2.0.1 → v2.3.0
cloud.google.com/go/dataqna: v0.8.1 → v0.8.4
cloud.google.com/go/datastore: v1.13.0 → v1.15.0
cloud.google.com/go/datastream: v1.10.0 → v1.10.3
cloud.google.com/go/deploy: v1.13.0 → v1.16.0
cloud.google.com/go/dialogflow: v1.40.0 → v1.47.0
cloud.google.com/go/dlp: v1.10.1 → v1.11.1
cloud.google.com/go/documentai: v1.22.0 → v1.23.7
cloud.google.com/go/domains: v0.9.1 → v0.9.4
cloud.google.com/go/edgecontainer: v1.1.1 → v1.1.4
cloud.google.com/go/essentialcontacts: v1.6.2 → v1.6.5
cloud.google.com/go/eventarc: v1.13.0 → v1.13.3
cloud.google.com/go/filestore: v1.7.1 → v1.8.0
cloud.google.com/go/firestore: v1.11.0 → v1.14.0
cloud.google.com/go/functions: v1.15.1 → v1.15.4
cloud.google.com/go/gkebackup: v1.3.0 → v1.3.4
cloud.google.com/go/gkeconnect: v0.8.1 → v0.8.4
cloud.google.com/go/gkehub: v0.14.1 → v0.14.4
cloud.google.com/go/gkemulticloud: v1.0.0 → v1.0.3
cloud.google.com/go/gsuiteaddons: v1.6.1 → v1.6.4
cloud.google.com/go/iam: v1.1.1 → v1.1.5
cloud.google.com/go/iap: v1.8.1 → v1.9.3
cloud.google.com/go/ids: v1.4.1 → v1.4.4
cloud.google.com/go/iot: v1.7.1 → v1.7.4
cloud.google.com/go/kms: v1.15.0 → v1.15.5
cloud.google.com/go/language: v1.10.1 → v1.12.2
cloud.google.com/go/lifesciences: v0.9.1 → v0.9.4
cloud.google.com/go/logging: v1.7.0 → v1.9.0
cloud.google.com/go/longrunning: v0.5.1 → v0.5.4
cloud.google.com/go/managedidentities: v1.6.1 → v1.6.4
cloud.google.com/go/maps: v1.4.0 → v1.6.2
cloud.google.com/go/mediatranslation: v0.8.1 → v0.8.4
cloud.google.com/go/memcache: v1.10.1 → v1.10.4
cloud.google.com/go/metastore: v1.12.0 → v1.13.3
cloud.google.com/go/monitoring: v1.15.1 → v1.17.0
cloud.google.com/go/networkconnectivity: v1.12.1 → v1.14.3
cloud.google.com/go/networkmanagement: v1.8.0 → v1.9.3
cloud.google.com/go/networksecurity: v0.9.1 → v0.9.4
cloud.google.com/go/notebooks: v1.9.1 → v1.11.2
cloud.google.com/go/optimization: v1.4.1 → v1.6.2
cloud.google.com/go/orchestration: v1.8.1 → v1.8.4
cloud.google.com/go/orgpolicy: v1.11.1 → v1.11.4
cloud.google.com/go/osconfig: v1.12.1 → v1.12.4
cloud.google.com/go/oslogin: v1.10.1 → v1.12.2
cloud.google.com/go/phishingprotection: v0.8.1 → v0.8.4
cloud.google.com/go/policytroubleshooter: v1.8.0 → v1.10.2
cloud.google.com/go/privatecatalog: v0.9.1 → v0.9.4
cloud.google.com/go/recaptchaenterprise/v2: v2.7.2 → v2.9.0
cloud.google.com/go/recommendationengine: v0.8.1 → v0.8.4
cloud.google.com/go/recommender: v1.10.1 → v1.12.0
cloud.google.com/go/redis: v1.13.1 → v1.14.1
cloud.google.com/go/resourcemanager: v1.9.1 → v1.9.4
cloud.google.com/go/resourcesettings: v1.6.1 → v1.6.4
cloud.google.com/go/retail: v1.14.1 → v1.14.4
cloud.google.com/go/run: v1.2.0 → v1.3.3
cloud.google.com/go/scheduler: v1.10.1 → v1.10.5
cloud.google.com/go/secretmanager: v1.11.1 → v1.11.4
cloud.google.com/go/security: v1.15.1 → v1.15.4
cloud.google.com/go/securitycenter: v1.23.0 → v1.24.3
cloud.google.com/go/servicedirectory: v1.11.0 → v1.11.3
cloud.google.com/go/shell: v1.7.1 → v1.7.4
cloud.google.com/go/spanner: v1.47.0 → v1.54.0
cloud.google.com/go/speech: v1.19.0 → v1.21.0
cloud.google.com/go/storagetransfer: v1.10.0 → v1.10.3
cloud.google.com/go/talent: v1.6.2 → v1.6.5
cloud.google.com/go/texttospeech: v1.7.1 → v1.7.4
cloud.google.com/go/tpu: v1.6.1 → v1.6.4
cloud.google.com/go/trace: v1.10.1 → v1.10.4
cloud.google.com/go/translate: v1.8.2 → v1.9.3
cloud.google.com/go/video: v1.19.0 → v1.20.3
cloud.google.com/go/videointelligence: v1.11.1 → v1.11.4
cloud.google.com/go/vision/v2: v2.7.2 → v2.7.5
cloud.google.com/go/vmmigration: v1.7.1 → v1.7.4
cloud.google.com/go/vmwareengine: v1.0.0 → v1.0.3
cloud.google.com/go/vpcaccess: v1.7.1 → v1.7.4
cloud.google.com/go/webrisk: v1.9.1 → v1.9.4
cloud.google.com/go/websecurityscanner: v1.6.1 → v1.6.4
cloud.google.com/go/workflows: v1.11.1 → v1.12.3
cloud.google.com/go: v0.110.6 → v0.111.0
github.com/asaskevich/govalidator: f61b66f → a9d515a
github.com/aws/aws-sdk-go: v1.44.331 → v1.49.13
github.com/cpuguy83/go-md2man/v2: v2.0.2 → v2.0.3
github.com/digitalocean/godo: v1.102.1 → v1.107.0
github.com/docker/distribution: v2.8.1+incompatible → v2.8.2+incompatible
github.com/docker/docker: v23.0.4+incompatible → v24.0.5+incompatible
github.com/emicklei/go-restful/v3: v3.9.0 → v3.11.0
github.com/envoyproxy/go-control-plane: 9239064 → v0.11.1
github.com/envoyproxy/protoc-gen-validate: v0.10.1 → v1.0.2
github.com/evanphx/json-patch/v5: v5.6.0 → v5.7.0
github.com/evanphx/json-patch: v5.6.0+incompatible → v5.7.0+incompatible
github.com/felixge/httpsnoop: v1.0.3 → v1.0.4
github.com/frankban/quicktest: v1.11.3 → v1.14.3
github.com/fsnotify/fsnotify: v1.6.0 → v1.7.0
github.com/go-asn1-ber/asn1-ber: v1.5.4 → v1.5.5
github.com/go-jose/go-jose/v3: v3.0.0 → v3.0.1
github.com/go-ldap/ldap/v3: v3.4.5 → v3.4.6
github.com/go-logr/logr: v1.2.4 → v1.4.1
github.com/go-logr/zapr: v1.2.4 → v1.3.0
github.com/go-openapi/jsonpointer: v0.19.6 → v0.20.2
github.com/go-openapi/jsonreference: v0.20.2 → v0.20.4
github.com/go-openapi/swag: v0.22.3 → v0.22.7
github.com/golang/glog: v1.1.0 → v1.1.2
github.com/golang/mock: v1.4.4 → v1.1.1
github.com/google/cel-go: v0.16.0 → v0.17.7
github.com/google/go-cmp: v0.5.9 → v0.6.0
github.com/google/go-pkcs11: v0.2.0 → c6f7932
github.com/google/s2a-go: v0.1.5 → v0.1.7
github.com/google/uuid: v1.3.0 → v1.5.0
github.com/googleapis/enterprise-certificate-proxy: v0.2.5 → v0.3.2
github.com/gorilla/websocket: v1.4.2 → v1.5.0
github.com/grpc-ecosystem/grpc-gateway/v2: v2.7.0 → v2.18.1
github.com/hashicorp/go-hclog: v1.4.0 → v1.5.0
github.com/hashicorp/go-plugin: v1.4.8 → v1.5.2
github.com/hashicorp/go-retryablehttp: v0.7.4 → v0.7.5
github.com/hashicorp/go-secure-stdlib/parseutil: v0.1.7 → v0.1.8
github.com/hashicorp/go-sockaddr: v1.0.2 → v1.0.6
github.com/hashicorp/vault/api: v1.9.2 → v1.10.0
github.com/hashicorp/vault/sdk: v0.9.2 → v0.10.2
github.com/hashicorp/yamux: 0bc27b2 → v0.1.1
github.com/imdario/mergo: v0.3.12 → v0.3.16
github.com/jmespath/go-jmespath: v0.4.0 → b0104c8
github.com/miekg/dns: v1.1.55 → v1.1.57
github.com/mitchellh/cli: v1.0.0 → v1.1.5
github.com/mitchellh/go-wordwrap: v1.0.0 → v1.0.1
github.com/onsi/ginkgo/v2: v2.12.0 → v2.13.0
github.com/onsi/gomega: v1.27.10 → v1.29.0
github.com/pavlo-v-chernykh/keystore-go/v4: v4.4.1 → v4.5.0
github.com/prometheus/client_golang: v1.16.0 → v1.18.0
github.com/prometheus/client_model: v0.4.0 → v0.5.0
github.com/prometheus/common: v0.44.0 → v0.45.0
github.com/prometheus/procfs: v0.10.1 → v0.12.0
github.com/rogpeppe/go-internal: v1.11.0 → v1.12.0
github.com/ryanuber/columnize: v2.1.0+incompatible → v2.1.2+incompatible
github.com/sirupsen/logrus: v1.9.0 → v1.9.3
github.com/spf13/cast: v1.3.0 → v1.3.1
github.com/spf13/cobra: v1.7.0 → v1.8.0
github.com/stoewer/go-strcase: v1.2.0 → v1.3.0
github.com/stretchr/objx: v0.5.0 → v0.5.1
github.com/urfave/cli/v2: v2.1.1 → v2.25.7
go.etcd.io/bbolt: v1.3.7 → v1.3.8
go.etcd.io/etcd/api/v3: v3.5.9 → v3.5.11
go.etcd.io/etcd/client/pkg/v3: v3.5.9 → v3.5.11
go.etcd.io/etcd/client/v2: v2.305.9 → v2.305.10
go.etcd.io/etcd/client/v3: v3.5.9 → v3.5.11
go.etcd.io/etcd/pkg/v3: v3.5.9 → v3.5.10
go.etcd.io/etcd/raft/v3: v3.5.9 → v3.5.10
go.etcd.io/etcd/server/v3: v3.5.9 → v3.5.10
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc: v0.35.0 → v0.46.1
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp: v0.39.0 → v0.46.1
go.opentelemetry.io/otel/exporters/otlp/internal/retry: v1.15.0 → v1.10.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc: v1.15.0 → v1.21.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace: v1.15.0 → v1.21.0
go.opentelemetry.io/otel/metric: v0.36.0 → v1.21.0
go.opentelemetry.io/otel/sdk: v1.15.0 → v1.21.0
go.opentelemetry.io/otel/trace: v1.15.0 → v1.21.0
go.opentelemetry.io/otel: v1.15.0 → v1.21.0
go.opentelemetry.io/proto/otlp: v0.19.0 → v1.0.0
go.uber.org/goleak: v1.2.1 → v1.3.0
go.uber.org/zap: v1.25.0 → v1.26.0
golang.org/x/crypto: v0.12.0 → v0.17.0
golang.org/x/exp: d852ddb → 02704c9
golang.org/x/lint: 738671d → d0100b6
golang.org/x/mod: v0.12.0 → v0.14.0
golang.org/x/net: v0.14.0 → v0.19.0
golang.org/x/oauth2: v0.11.0 → v0.15.0
golang.org/x/sync: v0.3.0 → v0.5.0
golang.org/x/sys: v0.11.0 → v0.15.0
golang.org/x/term: v0.11.0 → v0.15.0
golang.org/x/text: v0.12.0 → v0.14.0
golang.org/x/time: v0.3.0 → v0.5.0
golang.org/x/tools: 74c255b → v0.16.1
google.golang.org/api: v0.138.0 → v0.154.0
google.golang.org/appengine: v1.6.7 → v1.6.8
google.golang.org/genproto/googleapis/api: f966b18 → 50ed04b
google.golang.org/genproto/googleapis/bytestream: 1744710 → 3a041ad
google.golang.org/genproto/googleapis/rpc: 1744710 → 50ed04b
google.golang.org/genproto: f966b18 → 50ed04b
google.golang.org/grpc: v1.57.0 → v1.60.1
google.golang.org/protobuf: v1.31.0 → v1.32.0
gopkg.in/ini.v1: v1.62.0 → v1.67.0
honnef.co/go/tools: v0.0.1-2020.1.4 → ea95bdf
k8s.io/api: v0.28.1 → v0.29.0
k8s.io/apiextensions-apiserver: v0.28.1 → v0.29.0
k8s.io/apimachinery: v0.28.1 → v0.29.0
k8s.io/apiserver: v0.28.1 → v0.29.0
k8s.io/client-go: v0.28.1 → v0.29.0
k8s.io/code-generator: v0.28.1 → v0.29.0
k8s.io/component-base: v0.28.1 → v0.29.0
k8s.io/gengo: c0856e2 → 9cce18d
k8s.io/klog/v2: v2.100.1 → v2.110.1
k8s.io/kms: v0.28.1 → v0.29.0
k8s.io/kube-aggregator: v0.28.1 → v0.29.0
k8s.io/kube-openapi: 14e4089 → eec4567
k8s.io/utils: 3b25d92 → e7106e6
sigs.k8s.io/apiserver-network-proxy/konnectivity-client: v0.1.2 → v0.29.0
sigs.k8s.io/controller-runtime: v0.16.0 → v0.16.3
sigs.k8s.io/gateway-api: v0.7.1 → v1.0.0
sigs.k8s.io/structured-merge-diff/v4: v4.3.0 → v4.4.1
sigs.k8s.io/yaml: v1.3.0 → v1.4.0
software.sslmate.com/src/go-pkcs12: v0.2.1 → v0.4.0

Removed

cloud.google.com/go/storage: v1.10.0
dmitri.shuralyov.com/gpu/mtl: 666a987
github.com/Azure/azure-sdk-for-go: v68.0.0+incompatible
github.com/Azure/go-autorest/autorest/adal: v0.9.23
github.com/Azure/go-autorest/autorest/date: v0.3.0
github.com/Azure/go-autorest/autorest/mocks: v0.4.2
github.com/Azure/go-autorest/autorest/to: v0.4.0
github.com/Azure/go-autorest/autorest/validation: v0.3.1
github.com/Azure/go-autorest/autorest: v0.11.29
github.com/Azure/go-autorest/logger: v0.2.1
github.com/Azure/go-autorest/tracing: v0.6.0
github.com/Azure/go-autorest: v14.2.0+incompatible
github.com/BurntSushi/xgb: 27f1227
github.com/OneOfOne/xxhash: v1.2.2
github.com/Venafi/vcert/v4: 69f417a
github.com/alecthomas/template: a0175ee
github.com/armon/circbuf: bbbad09
github.com/benbjohnson/clock: v1.3.0
github.com/bketelsen/crypt: 5cbc8cc
github.com/cespare/xxhash: v1.1.0
github.com/coreos/bbolt: v1.3.2
github.com/coreos/etcd: v3.3.13+incompatible
github.com/coreos/go-systemd: 95778df
github.com/coreos/pkg: 399ea9e
github.com/dgrijalva/jwt-go: v3.2.0+incompatible
github.com/dgryski/go-sip13: e10d5fe
github.com/ghodss/yaml: v1.0.0
github.com/go-gl/glfw/v3.3/glfw: 6f7a984
github.com/go-gl/glfw: e6da0ac
github.com/go-kit/kit: v0.8.0
github.com/go-stack/stack: v1.8.0
github.com/google/gnostic: v0.5.7-v3refs
github.com/google/martian/v3: v3.0.0
github.com/google/martian: v2.1.0+incompatible
github.com/google/renameio: v0.1.0
github.com/hashicorp/consul/api: v1.1.0
github.com/hashicorp/consul/sdk: v0.1.1
github.com/hashicorp/go-msgpack: v0.5.3
github.com/hashicorp/go-syslog: v1.0.0
github.com/hashicorp/go.net: v0.0.1
github.com/hashicorp/logutils: v1.0.0
github.com/hashicorp/mdns: v1.0.0
github.com/hashicorp/memberlist: v0.1.3
github.com/hashicorp/serf: v0.8.2
github.com/jstemmer/go-junit-report: v0.9.1
github.com/kr/logfmt: b84e30a
github.com/mitchellh/gox: v0.4.0
github.com/mitchellh/iochan: v1.0.0
github.com/morikuni/aec: v1.0.0
github.com/oklog/ulid: v1.3.1
github.com/pascaldekloe/goe: 57f6aae
github.com/prometheus/tsdb: v0.7.1
github.com/sean-/seed: e2103e2
github.com/shurcooL/sanitized_anchor_name: v1.0.0
github.com/spaolacci/murmur3: f09979e
golang.org/x/image: cff245a
golang.org/x/mobile: d2bd2a2
gopkg.in/alecthomas/kingpin.v2: v2.2.6
gopkg.in/resty.v1: v1.12.0
gotest.tools/v3: v3.4.0
rsc.io/binaryregexp: v0.2.0
rsc.io/quote/v3: v3.1.0
rsc.io/sampler: v1.3.0

Release 1.14

Known Issues

ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured - #6755, #6757

Workarounds

v1.14.7

Bugfixes

Other (Cleanup or Flake)

v1.14.6

Changes by Kind

Other (Cleanup or Flake)

v1.14.5

Known Issues

Changes

Bug or Regression

v1.14.4

Changes since v1.14.3

Bug or Regression

Other (Cleanup or Flake)

v1.14.3

Changes since v1.14.2

Bug or Regression

v1.14.2

Changes since v1.14.1

Bug or Regression

Other (Cleanup or Flake)

v1.14.1

Changes since v1.14.0

Bug or Regression

v1.14.0

Known Issues

Breaking Changes

Major Themes

New X.509 Features

New CA certificate Features

Security

Other

Community

Changes

Feature

Bug or Regression

Other (Cleanup or Flake)

Dependencies

Added

Changed

Removed

ACME Issuer (Let's Encrypt): wrong certificate chain may be used if `preferredChain` is configured - #6755, #6757

`v1.14.7`

`v1.14.6`

`v1.14.5`

`v1.14.4`

Changes since `v1.14.3`

`v1.14.3`

Changes since `v1.14.2`

`v1.14.2`

Changes since `v1.14.1`

`v1.14.1`

Changes since `v1.14.0`

`v1.14.0`