Gloo Network for Cilium versions
View supported Gloo Network versions and their release cycle.
Supported versions
Solo supports n-3 versions of Gloo Network for Cilium. Within each Gloo Network version, different open source project versions are supported, including n-4 version support for Solo distributions of Cilium.
The following versions of Gloo Network are supported with the compatible Solo versions of Cilium. Later versions of the open source project that are released after Gloo Network might also work, but are not tested as part of the Gloo Network release.
| Gloo Network | Release date | Supported Solo distributions of Cilium versions tested by Solo |
|---|---|---|
| 2.5 | 09 Jan 2024 | Cilium 1.12 - 1.14 on Kubernetes 1.22 - 1.28 |
Solo distributions of Cilium
The Solo distribution of Cilium is a hardened Cilium enterprise image, which maintains support for security patches to address Common Vulnerabilities and Exposures (CVEs) and other security fixes.
Keep in mind that Gloo Network offers security patching support only with Solo distributions of Cilium versions, not community Cilium versions. Solo distributions of Cilium versions support the same patch versions as community Cilium. You can review community Cilium patch versions in the Cilium release documentation. To get the backported Cilium support, you must run the latest Gloo Network patch version.
To download the Solo distribution of a Cilium image, you must be a registered user and be able to log in to the Solo Support Center. Open the Cilium images built by Solo.io support article. When prompted, log in to the Support Center with your Solo account credentials.
Release lifecycle
Solo supports n-3 for Gloo Network and n-4 for Solo distributions of Cilium.
Typically, Gloo Network releases a new minor version, n, each quarter. When the new minor version is released, the previous n-4 for Gloo Network or n-5 for Solo distributions of Cilium become 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.
| Version | Supported? | Type | Description |
|---|---|---|---|
n | 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. |
n-2n-3Cilium only: n-4 | Yes | Stable | Supported versions up to n-3 (and n-4 for Solo distributions of Cilium) continue to receive support for security patches, bugs, and documentation. |
n+1 | No | Beta | Active feature development happens on the main branch as part of the development of a beta version. When the n+1 beta version is prepared as a release candidate, new feature development is suspended until this version becomes the new n. New features and development work on main is subject to change, not necessarily fully tested, and not supported. |
n-4Cilium only: n-5 | No | Unsupported | Versions that are n-4 (and n-5 for Solo distributions of Cilium) or older are no longer supported or maintained. Upgrade your release to a stable version to continue to receive support. |
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.
| Comparison point | Alpha | Beta | GA |
|---|---|---|---|
| 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 |
Feature gates
To review the required Gloo versions for specific features that you can optionally enable, see Feature gates.
Open source packages in Gloo Network
For specific versions of open sources packages that are bundled with Gloo Network, 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
Refer to the Install FIPS-compliant images guide.