Skip to content
If you are interested in trying out Gloo Gateway with the Kubernetes Gateway API, check out Solo Enterprise for kgateway. This version adds enterprise functionality on top of the kgateway open source project.

Release notes

Page as Markdown
Review summaries of the main changes in the Gloo Gateway 1.20 release.
Make sure that you review the breaking changes 🔥 that were introduced in this release and the impact that they have on your current environment.
Introduction

The release notes include important installation changes and known issues. They also highlight ways that you can take advantage of new features or enhancements to improve your product usage.
For more information, see the following related resources:
🔥 Breaking changes

Review details about the following breaking changes. To review when breaking changes were released, you can use the comparison feature of the open source changelog or enterprise changelog. The severity is intended as a guide to help you assess how much attention to pay to this area during the upgrade, but can vary depending on your environment.
🚨 High

Review severe changes that can impact production and require manual intervention.
AuthPlugin removed

The AuthPlugin auth config type is removed in 1.20. If you use this config type, you must remove it from your Helm values file before upgrading Gloo Gateway. If you need to configure your own auth server, check out the Passthrough auth guides instead.
Discovery disabled by default

To improve performance, service discovery is now disabled by default in the Gloo Gateway Helm chart. In the example Helm values in all installation guides for Gloo Gateway with the Kubernetes Gateway API, discovery is set to false. However, if you use discovery, ensure that the discovery.enabled=true for Gloo Gateway OSS or gloo.discovery.enabled=true for Gloo Gateway Enterprise fields are explicitly set to true before you upgrade. For more information, see the discovery overview.
Envoy version upgrade

The Envoy dependency in Gloo Gateway 1.20 was upgraded from 1.33.x to 1.35.x. This change includes the following upstream breaking changes.
Envoy 1.34:
For more information about these changes, see the Envoy changelog documentation.
  • Extproc - Tracing changes: When the modeOverride fields of the header and trailer modes have the value DEFAULT or are unset, no change is made to the processing mode that is set in the filter configuration. Additionally, a bug was fixed in which local replies were incorrectly sent to the extProc server for external processing. You can temporarily revert this change by setting the runtime guard field envoy.reloadable_features.skip_ext_proc_on_local_reply to false.
  • TLS - Envoy FIPS: The Envoy FIPS build is updated to use the same version of BoringSSL as the Envoy standard build to meet the requirements of the revised FedRAMP policy. Default values might have changed in the encryption settings due to the large version bump.
  • HTTP connection manager - Generate request ID: When the x-request-id header is empty, generateRequestId now generates a request ID on the request. Previously, it only generated an ID when the header was missing.
  • Formatters: The %CEL% and %METADATA% formatters are now considered built-in, and can be used directly in substitution format strings if the related extensions are linked.
Envoy 1.35:
For more information about these changes, see the Envoy changelog documentation.
  • Tracing changes: Added max_cache_size to the OpenTelemetry tracer config. This limits the number of spans that can be cached before the cache is flushed. The default is 1024 spans. Previously, flushing only happened at the interval that you set. You can change this setting based on the expected telemetry volume in your environment.
Caching filter deprecated

The caching filter is deprecated and planned to be removed in Gloo Gateway version 1.21.
🔔 Medium

Review changes that might have impact to production and require manual intervention, but possibly not until the next version is released.
  • No medium-severity changes are currently reported.
ℹ️ Low

Review informational updates that you might want to implement but that are unlikely to materially impact production.
  • No low-severity changes are currently reported.
⚒️ Installation changes

In addition to comparing differences across versions in the changelog, review the following installation changes from the previous minor version to version 1.20.
  • No installation changes are currently reported.
🌟 New features

Review the following new features that are introduced in version 1.20 and that you can enable in your environment.
Amazon Bedrock in Gloo AI Gateway

Amazon Bedrock is now supported as an LLM provider with Gloo AI Gateway. For more information, see the Amazon Bedrock docs.
Open source
Was this page helpful?