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.

  • No high-severity changes are currently reported.

🔔 Medium

Review changes that might have impact to production and require manual intervention, but possibly not until the next version is released.

Envoy version 1.36 upgrade

The Envoy dependency in Gloo Gateway 1.21 was upgraded from 1.35.x to 1.36.x. This upgrade includes the following changes. For more information about these changes, see the Envoy changelog documentation.

  • http: A route refresh will now result in a tracing refresh. The trace sampling decision and decoration of the new route will be applied to the active span. In Envoy, this change is controlled by the runtime guard envoy.reloadable_features.trace_refresh_after_route_refresh. Note, if pack_trace_reason is set to true (it is true by default), a request marked as traced cannot be unmarked as traced after the tracing refresh.
  • http2: The default value for the maximum number of concurrent streams in HTTP/2 has been changed from 2147483647 to 1024. The default value for the initial stream window size in HTTP/2 has been changed from 256MiB to 16MiB. The default value for the initial connection window size in HTTP/2 has been changed from 256MiB to 24MiB. In Envoy, this change is controlled by the runtime guard envoy.reloadable_features.safe_http2_options. These values can also be set using HTTP Connection Manager (HCM) settings
  • formatter: Deprecated legacy header formatter support for %DYNAMIC_METADATA(["namespace", "key", ...])%, %UPSTREAM_METADATA(["namespace", "key", ...])% and %PER_REQUEST_STATE(key)%. Instead, use %DYNAMIC_METADATA(namespace:key:...])%, %UPSTREAM_METADATA(namespace:key:...])% and %FILTER_STATE(key:PLAIN)% as alternatives. In Envoy, this change is controlled by the runtime guard envoy.reloadable_features.remove_legacy_route_formatter. The flag defaults to false for now, but after two release periods is planned to be flipped to true.
  • jwt_authn: Removed runtime guard envoy.reloadable_features.jwt_authn_remove_jwt_from_query_params and legacy code paths. This guard was introduced in Envoy v1.31 (Gloo Gateway v1.18) and is no longer available in Gloo Gateway v1.21.
  • jwt_authn: Removed runtime guard envoy.reloadable_features.jwt_authn_validate_uri and legacy code paths. This guard was introduced in Envoy v1.31 (Gloo Gateway v1.18) and is no longer available in Gloo Gateway v1.21.

ℹī¸ 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.21.

  • No installation changes are currently reported.

🌟 New features

Review the following new features that are introduced in version 1.21 and that you can enable in your environment.

🔄 Feature changes

Review the following changes that might impact how you use certain features in your Gloo Gateway environment.

  • No feature changes are currently reported.