All add-ons · Gateway API
Is Envoy Gateway compatible with Kubernetes 1.37?
Gateway API implementation on Envoy. The project publishes a compatibility matrix of Envoy Gateway, Envoy, Gateway API, and Kubernetes versions.
Gateway API v1.6.1. Envoy Proxy distroless-v1.40.x. End of life 2027/05/05. Upgrade Gateway API CRDs to v1.6 before this release.
Supported combinations: v1.10 uses Gateway API v1.6.1 and Kubernetes v1.34, v1.35, v1.36, v1.37, with end of life 2027/05/05. v1.9 uses Gateway API v1.6.1 and Kubernetes v1.33–v1.36, end of life 2027/02/14. v1.8 uses Gateway API v1.5.1 and Kubernetes v1.32–v1.35, end of life 2026/11/08.
Version grid
| Envoy Gateway | 1.31 | 1.32 | 1.33 | 1.34 | 1.35 | 1.36 | 1.37 |
|---|---|---|---|---|---|---|---|
| 1.10 · current | Not supported | Not supported | Not supported | Supported | Supported | Supported | Supported |
| 1.9 | Not supported | Not supported | Supported | Supported | Supported | Supported | Not supported |
| 1.8 · deprecated | Not supported | Supported | Supported | Supported | Supported | Not supported | Not supported |
Empty-looking “not in the published matrix” cells were not listed by the project. They are not a guess that the combination fails.
Notes
The Helm install docs for the current release say Gateway API v1.6 CRDs must be upgraded before Envoy Gateway, because TCPRoute and UDPRoute moved to gateway.networking.k8s.io/v1. Standard-channel v1alpha2 is no longer served. Helm chart name is gateway-helm.
Sources
Last checked 2026-11-15. Latest GitHub release v1.10.0 (opens in a new tab) (2026-11-06).
Project site: https://gateway.envoyproxy.io (opens in a new tab)
Managed Kubernetes end of support
Addon compatibility is not the same as the platform’s support window. End-of-support dates for the managed services are on EOL Radar: Amazon EKS (opens in a new tab), Azure AKS (opens in a new tab), Google Kubernetes Engine (opens in a new tab).