Changelog
Your clusters must run Gloo Mesh Enterprise version 2.1.4 before you can upgrade to version 2.2.4.
You must always upgrade the Gloo management server before upgrading the Gloo agent to avoid unexpected behavior. Note that only n-1 minor version skew is supported between the management server and the agent. For more information, see the Skew policy. For upgrade instructions, see Upgrade Gloo Mesh.
Review the changelog for Gloo Platform releases. 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.
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:
- Do not use underscores (
_) in the names of your clusters or in thekubeconfigcontext for your clusters. - You can deploy Gloo Platform in a single cluster or multicluster setup. However, the single cluster setup has not been tested as extensively. If you run into issues, try Debugging Gloo and Getting help and support.
- For Gloo Mesh Enterprise 2.2.0 or 2.2.1 on macOS X Ventura 13.0, UPX-compressed amd64 and x86_64 executables do not work and result in a segmentation fault error. To use
meshctlon macOS Ventura, either upgrade to Gloo Mesh 2.2.2 or later, or see the specific install instructions for 2.2.0 or 2.2.1. - 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.
- Istio versions 1.13.0 - 1.13.3 have a known issue about service entry hostname expansion. The issue is resolved in Istio 1.13.4.
- Automatic rotation of Gloo Platform relay and Istio root certificates is not supported. If your certificates are about to expire, contact your Solo account representative to start the certificate rotation process.