Gloo Platform changelog

Review the changelog for Gloo Platform releases.

Changelog entry types

Changelog entries are categorized into the following types:

• Dependency Bumps: The version for a dependency in Gloo Platform is bumped in this release. Be sure to check for any Breaking Change entries that accompany a dependency bump.
• Breaking Changes: An API is changed in a way that is not backwards compatible, such as a changed format for an API field. Occasionally, a breaking change occurs for the process to upgrade Gloo, in which the changelog entry indicates how to use the new upgrade process.
• Helm Changes: The installation Helm chart is changed. If this change is not backwards compatible, an accompanying Breaking Change entry is indicated for the release.
• New Features: A new feature is implemented in the release.
• Fixes: A bug is resolved in this release.

Installation changes

In addition to comparing differences across versions in the changelog, review the following installation changes from previous versions to version 2.5.

• Gloo component stats port: The glooMgmtServer.statsPort and glooAgent.ports.stats changed from 9091 to 9093.
• Default Gloo Platform add-ons namespace removed: In previous releases, all add-ons were automatically installed to the gloo-mesh-addons namespace unless you specified a different namespace during the Gloo Mesh Enterprise installation. Starting with release v2.5.0, this default value is removed. If no value is set in the common.addonsNamespace Helm field, your add-ons are now deployed to the namespace that the Helm release is installed to. To avoid disruptions or downtime for your add-on components, such as a rate limit server, set the namespace you want your add-ons to be installed to in the common.addonsNamespace field of your Helm values file.

Known issues

The Solo team fixes bugs, delivers new features, and makes changes on a regular basis as described in the changelog. Some issues, however, might impact many users for common use cases. These known issues are as follows:

• Cluster names: Do not use underscores (_) in the names of your clusters or in the kubeconfig context for your clusters.
• Gloo UI: The Gloo UI cannot run on IPv4-only nodes where IPv6 is explicitly disabled.
• OTel pipeline: FIPS-compliant builds are not currently supported for the OTel collector agent image.
• Istio:
  • The WasmDeploymentPolicy Gloo CR is currently unsupported in Istio version 1.18.
  • Istio versions 1.17 and later and Gloo Platform 2.4 and later do not support the Gloo legacy metrics pipeline. If you run the legacy metrics pipeline, be sure that you set up the Gloo OpenTelemetry (OTel) pipeline instead in your new or existing Gloo Gateway installation.
  • For FIPS-compliant builds of Istio 1.17.2 and 1.16.4, you must use the -patch1 versions of the latest Istio builds published by Solo, such as 1.17.2-patch1-solo-fips for Solo Istio version 1.17. These patch versions fix a FIPS-related issue introduced in the upstream Envoy code. In 1.17.3 and later, FIPS compliance is available in the -fips tags of regular Solo Istio builds, such as 1.17.3-solo-fips.
  • Istio versions 1.14.0 - 1.14.3 have a known issue about unused endpoints failing to be deleted. Additionally, version 1.14.4 has a known issue about short hostnames causing Kubernetes service and ServiceEntry conflicts. Both issues are resolved in Istio 1.14.5.
• GraphQL: For known issues regarding the GraphQL module, see the GraphQL documentation.
• Portal: For known issues regarding the developer portal, see the Portal documentation.

Changelog