Provider Status¶
Several Service Mesh and Gateway solutions are already implementing the Gateway API. You can find a contributed list of known implementations at the Gateway API website.
All providers should work out of the box with Argo Rollouts and the Gateway plugin.
Warning
Notice that with 0.x implementations of the Gateway API, only the 0.2.0 release of the
plugin will work. Versions from 0.3.0 and upwards need a v1.0+ implementation
to work. Plugin version 0.2.0 uses v1beta1 resources while 0.3.0 needs gateway.networking.k8s.io/v1 resources
For convenience we are including here a list of those actually tested with the plugin along with the related example (if applicable).
| Provider | Version | API Version | Plugin | Code |
|---|---|---|---|---|
| Amazon VPC Lattice | 1.1.2 | 1.3.0 | 0.6.0 | Example |
| Cilium | 1.18.2 | 1.2.0 | 0.8.0 | Example |
| Envoy Gateway | 0.5.0 | Unknown | 0.2.0 | Example |
| Gloo Gateway | 2.0.0-beta | 1.0 | 0.2.0 | Example |
| Google Cloud | N/A | 0.7.0 | 0.2.0 | Example |
| Kong | 2.9.x | 0.7.1 | 0.2.0 | Example |
| Linkerd | edge-25.9.4 | 1.2.1 | 0.8.0 | Example |
| NGINX Gateway | Unknown | 0.8.0 | 0.2.0 | Example |
| Traefik | 3.1.3 | 1.1 | 0.4.0 | Example |
Note that these examples are included just for completeness. You should be able to use any solution that implements the Gateway API.
Note
We are always looking for more tested implementations. If you have tried the plugin with a provider not listed above please open a Pull Request to add it to the list.