Skip to content
Latest (currently 2026.7.1) has the newest features, bug fixes, and CVE patches of Solo Enterprise for agentgateway.

For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Version support

Page as Markdown

View supported versions and their release cycle.

Supported versions

Review information about the support and compatibility of Solo Enterprise for agentgateway.

Support matrix

Review the following information about supported release versions for Solo Enterprise for agentgateway.

Solo Enterprise for agentgatewayDateLTS?Bug fixes untilCVEs until
2026.7.1-patch.x30 Jul 2026Oct 2026Jun 2027
2.3.x09 Apr 2026Jul 2026Apr 2027

Compatibility matrix

Review the following table that shows the compatibility matrix for the different versions of Solo Enterprise for agentgateway with related projects.

Solo Enterprise for agentgatewayKubernetes*Gateway API StandardGateway API Experimentalagentgateway OSSMCP specIstio§Solo UI
2026.7.1-patch.x1.32 - 1.361.4 - 1.61.6Up to this commit ID2026-07-281.26 - 1.290.5.3
2.3.x1.31 - 1.351.3 - 1.51.5Up to this commit ID2025-06-181.26 - 1.290.5.3

* Solo Enterprise for agentgateway is supported and tested with the latest Kubernetes version at the time of the Solo Enterprise for agentgateway release, and all Kubernetes versions that were released up to 1 year before the latest version.

Gateway API: The upstream agentgateway project is conformant to the Kubernetes Gateway API specification.
  • The Standard channel versions are supported and tested for the given Solo Enterprise for agentgateway release.
  • The Experimental channel of the highest supported Standard channel version of a release is compatible with Solo Enterprise for agentgateway. Experimental channel features from other Gateway API versions, such as XListenerSet from a version other than the highest supported Standard channel version, are not guaranteed to be compatible.

Agentgateway supports the MCP spec at the listed version. Earlier versions might also work, but are not guaranteed. Make sure that your MCP clients are not running at a more recent version than your MCP servers.For more information, see MCP spec compatibility.

§ Istio must run on a compatible version of Kubernetes. For example, Istio 1.29 is tested, but not supported, on Kubernetes 1.30. For more information, see the Istio docs.

Release versioning

As of 2026.5.0, Solo Enterprise for agentgateway uses calendar versioning, or calver, (YYYY.MM.micro).

Note

The upstream agentgateway project continues to use semantic versioning, or semver, (n.n.n).

Release cadence

New versions are released as they become available, typically on a weekly basis. Each release follows the calver formatting and increases the micro version by 1.

For example:

  • The first release in July 2026 is 2026.7.0.
  • The next release in July 2026 is 2026.7.1.
  • If the next release still happens in July, then it is 2026.7.2.
  • If the next release happens in August, then it is 2026.8.0.
  • Once a quarter, a release is marked for long-term support (LTS). The LTS release coincides with the latest release for a brief time, and is pinned to a particular micro version, such as 2026.7.1.
  • Bug fixes and CVE patches are suffixed to the LTS release version and do not increase the micro version. For example, a patch for the quarterly LTS release in July 2026 that was released after 2026.7.1 is formatted as 2026.7.1-patch.0, not 2026.7.2.

Release streams

Release streams, sometimes also called channels, give you the flexibility to adopt the latest Solo Enterprise for agentgateway features at your own pace.

StreamWhat it includesUpgrade frequency
LatestThe most recent features, bug fixes, and CVE patches.Upgrade with each new releases so you get the latest features, bug fixes, and CVE patches.
LTS
  • The features at the time of the release.
  • Bug fixes until the next quarterly release becomes available, for roughly 3 months.
  • CVE patches for 12 months after their release date.
Apply bug and security patches as they become available. Upgrade to the latest stream whenever you want the newest features.

Example release scenario

Flip through the following hypothetical release scenarios.

As each new release becomes available, the latest supported version gets updated with the latest features, bug fixes, and CVE patches.

  • The latest release is 2026.6.3.
  • Older releases no longer have the latest features, bug fixes, and CVE patches.

Once a quarter, a release is designated for long-term support (LTS). This release gets bug fixes until the next LTS release and CVE patches for a year.

  • The latest release is 2026.7.1.
  • The 2026.7.1-patch.0 release is designated as the first LTS patch off 2026.7.1.
  • LTS releases continue to get patches, such as 2026.7.1-patch.1 and 2026.7.1-patch.2.

Each stream gets more releases over time.

  • In the latest stream, only the most recent release has the latest features, bug fixes, and CVE patches.
  • In the LTS stream, several releases are supported at the same time.
  • 2026.7.1-patch.N has the features from July 2026, bug fixes until the 2026.10.3 LTS release, and CVE patches for a year.
  • 2026.10.3-patch.N has the features from October 2026, bug fixes until the 2027.1.2 LTS release, and CVE patches for a year.
  • 2027.1.2-patch.N has the features from January 2027, bug fixes until the next LTS release, and CVE patches for a year.

Additional support

Have other questions? Reach out to us on Slack or email sales@solo.io.