This document tracks downstream implementations of Gateway API and provides status and resource references for them.
Implementors of Gateway API are encouraged to update this document with status information about their implementations, the versions they cover, and documentation to help users get started.
- Apache APISIX (work in progress)
- Contour (alpha)
- Emissary-Ingress (Ambassador API Gateway) (alpha)
- Gloo Edge 2.0 (work in progress)
- Google Kubernetes Engine (public preview)
- HAProxy Ingress (alpha)
- Istio (alpha)
- Kong (work in progress)
- Traefik (alpha)
In this section you will find specific links to blog posts, documentation and other Gateway API references for specific implementations.
Apache APISIX is a dynamic, real-time, high-performance API Gateway. APISIX provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more.
APISIX is moving forward to implement the Gateway API
v1alpha2 version of the specification for its Apache APISIX Ingress Controller, and status updates and documentation will be provided here as the work progresses.
Contour is an open source ingress controller for Kubernetes.
Contour currently implements much of Gateway API
See the Contour Gateway API Guide for information on how to deploy and use Contour's Gateway implementation.
Note that not all of the
v0.3.0 specification is completed yet, contributions welcome!.
Emissary-Ingress (Ambassador API Gateway)¶
Emissary-Ingress (formerly known as Ambassador API Gateway) is an open source CNCF project that provides an ingress controller and API gateway for Kubernetes built on top of Envoy Proxy. See here for more details on using the Gateway API with Emissary.
Gloo Edge 2.0 is an Istio-native, fully-featured Envoy based API gateway that brings Gloo Edge functionality to Istio. The Solo.io team is actively working towards an implementation of the Gateway API.
Google Kubernetes Engine¶
Google Kubernetes Engine (GKE) is a managed Kubernetes platform offered by Google Cloud. GKE's implementation of the Gateway API is through the GKE Gateway controller (currently in Preview) which provisions Google Cloud Load Balancers for Pods in GKE clusters.
The GKE Gateway controller supports weighted traffic splitting, mirroring, advanced routing, multi-cluster load balancing and more. See the docs to deploy private or public Gateways and also multi-cluster Gateways.
HAProxy Ingress is a community driven ingress controller implementation for HAProxy.
HAProxy Ingress v0.13 partially supports the Gateway API's v1alpha1 specification. See the controller's Gateway API documentation to get informed about conformance and roadmap.
Istio is actively working towards an implementation of the Gateway API and you can use the Istio Gateway API Documentation to deploy the Istio Gateway API in it's current state.
Kong is an open source API Gateway built for hybrid and multi-cloud environments.
Kong is actively working towards an implementation of the Gateway API
v0.2.x specification for it's Kubernetes Ingress Controller and status updates and documentation will be provided here as the work progresses.
Traefik is an open source cloud-native application proxy.
Traefik currently supports the previous
v0.1.x Gateway API specification, check the Kubernetes Gateway Documentation for information on how to deploy and use Traefik's Gateway implementation.
Traefik is currently working on implementing TCP, status updates and documentation will be provided here as the work progresses.