Gloo Mesh Core versions
View supported Gloo Mesh Core versions and their release cycle.
n-3 versions for Gloo Mesh Core. Within each Gloo Mesh Core version, different open source project versions are supported, including Solo Istio
n-4 version support.
The following versions of Gloo Mesh Core are supported with the compatible open source project versions of Istio and Kubernetes. Later versions of the open source projects that are released after Gloo Mesh Core might also work, but are not tested as part of the Gloo Mesh Core release.
|Gloo Mesh Core||Release date||Supported Solo Istio versions and related Kubernetes versions tested by Solo|
Solo Istio distributions
For information about Solo Istio, see the Solo Istio version reference.
n-3 for Gloo Mesh Core and
n-4 for Solo Istio versions.
Typically, Gloo Mesh Core releases a new minor version,
n, each quarter. When the new minor version is released, the previous
n-4 for Gloo Mesh Core or
n-5 for Solo Istio becomes unsupported. Make sure that you run a supported version for production environments, and keep that version upgraded to the latest patch version so that you have the latest security fixes. For more information, see the upgrade guide.
|Yes||Latest||The latest stable version is the default version when you view the documentation. New features are typically not developed for the latest version, but the version is actively maintained for security patches, bugs, and documentation.|
|Yes||Stable||Supported versions up to |
|No||Beta||Active feature development happens on the |
|No||Unsupported||Versions that are |
Gloo feature maturity
Solo periodically provides new features in minor releases of Gloo versions. To receive feedback and improve functionality for real use cases, these features are often released according to a feature maturity model. As the features are improved and stabilized, they are gradually moved through the stages of alpha, beta, and general availability (GA) support. Review the following table for the comparison points between each stage of feature maturity. To see the maturity of a feature, check the feature’s documentation.
|API||Can and will likely change||Unlikely to change||No change|
|Implementation||Can and will likely change||Can change, but user experience is maintained||No changes that affect user experience|
|Upgrade paths||Not guaranteed||Not guaranteed||Provided and tested|
|Requests for enhancement (RFEs) and bug fixes||RFEs and bug fixes prioritized||RFEs and bug fixes prioritized||Fully supported|
|Documentation||Not guaranteed and supplied with warnings||Supplied with warnings||Fully supplied|
|Automated testing||Internal testing, but little testing with real use cases||Internal testing and some testing with real use cases||Fully tested and validated with real use cases|
|Suggested usage||Exploration and feedback||Testing setups, demos, and POCs||Production setups|
Open source packages in Gloo Mesh Core
For specific versions of open sources packages that are bundled with Gloo Mesh Core, see the entries in the open source attribution. For more information on where these open source packages are retrieved from, see the go.mod documentation.
Download a specific image
You can download a particular image for Gloo Mesh Core, such as for the following use cases.
- To download and transfer these images if your environment does not have public network access or cannot pull public images, for an air-gapped installation.
- To use a custom build that aligns with compliance standards such as Federal Information Processing Standards (FIPS).
- Get the version tag that you want to use.
- To download the package for all Gloo components that you deploy in your management and workload clusters, append the
<version_tag>to the following URL.
- Optional: For FIPS-compliant images, open the
values.yamlfile in the downloaded package, search for the
imagesection, and append
-fipsto the tag, such as in the following example.
... glooMeshMgmtServer: image: pullPolicy: IfNotPresent registry: gcr.io/gloo-mesh repository: gloo-mesh-mgmt-server tag: 2.5.0-beta2-fips
- Optional: If you need to pull the images locally, such as for an air-gapped installation, you can use the information you retrieved from the
imagessection in the
values.yamlfile to pull the image. For example, you might use the following
docker pullcommand for a FIPS image. Repeat this step for each image that you want to build locally and push to a private repository.
docker pull gcr.io/gloo-mesh/gloo-mesh-mgmt-server:2.5.0-beta2-fips
- Use these packages when you install Gloo Mesh Core.