Version support
Review the following information about supported release versions for the agentgateway project.
Supported versions
agentgateway* |
Release date | Kubernetes | Gateway API† |
Helm | Istio‡ |
|---|---|---|---|---|---|
| 2.2.x | 09 Feb 2026 | 1.31 - 1.35 | 1.4.x | >= 3.12 | 1.23 - 1.27 |
* Agentgateway versions: Agentgateway on Kubernetes uses the kgateway control plane for tasks such as translating resources from Gateway API to agentgateway proxy configuration. As such, the versioning for agentgateway aligns with kgateway releases. Note that version 2.2 of agentgateway on Kubernetes is the last version to use the kgateway control plane. The next release plans to standardize the versioning for standalone agentgateway and agentgateway on Kubernetes.
† Gateway API versions: The agentgateway project is conformant to the Kubernetes Gateway API specification. For more details, see the Gateway API docs and agentgateway conformance report per version, such as Gateway API v1.4.0.
‡ Istio versions: Istio must run on a compatible version of Kubernetes. For example, Istio 1.27 is tested, but not supported, on Kubernetes 1.28. For more information, see the Istio docs.
Release cadence
Stable builds for agentgateway on Kubernetes are released as minor versions. A stable branch for a minor version, such as 2.2, is tagged from main, and stable builds are supported from that branch.
Release development
New features for agentgateway are developed on main and available as development builds. Stable branches are created off of main for each minor version, such as v2.2.x.
Release process
Development of a quality stable release on main typically follows this process:
- New feature development is suspended on
main. - Release candidates are created, such as
2.2.0-rc1,2.2.0-rc2, and so on. - A full suite of tests is performed for each release candidate. Testing includes all documented workflows, a test matrix of all supported platforms, and more.
- Documentation for that release is prepared, vetted, and staged.
- The stable minor version is released as part of a stable branch, such as
v2.0.x. - Feature development on
mainis resumed.
Feature development on main branch
Feature development is performed on the main branch. Upon a merge to main, a development build is automatically released. The current development release is 2.3.0-main.
Backports to stable branches
New features are not developed on or backported to stable branches, such as v2.0.x. However, critical patches, bug fixes, and documentation fixes are backported as needed.
Experimental features in Gateway API
The following features are experimental in the upstream Kubernetes Gateway API project, and are subject to change.
| Feature | Minimum Gateway API version |
|---|---|
| ListenerSets | 1.3 |
| TCPRoutes | 1.3 |
| BackendTLSPolicy | 1.4 |
| CORS policies | 1.2 |
| Retries | 1.2 |
| Session persistence | 1.3 |
| HTTPRoute rule attachment option | 1.3 |
Experimental feature gate: To use experimental Gateway API features in agentgateway version 2.2 or later, you must enable the KGW_ENABLE_GATEWAY_API_EXPERIMENTAL_FEATURES environment variable in your agentgateway controller deployment. This setting defaults to false and must be explicitly enabled. For example, you might upgrade your installation with the following Helm value:
controller:
extraEnv:
KGW_ENABLE_GATEWAY_API_EXPERIMENTAL_FEATURES: "true"Sample command for version 1.4.0: Note that some CRDs are prefixed with X to indicate that the entire CRD is experimental and subject to change.
kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/experimental-install.yaml