1# Implementations
2
3This document tracks downstream implementations and integrations of Gateway API and provides status and resource references for them.
4
5Implementors and integrators 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.
6
7## Gateway Controller Implementation Status <a name="gateways"></a>
8
9- [Acnodal EPIC][1] (public preview)
10- [Amazon Elastic Kubernetes Service][23] (alpha)
11- [Apache APISIX][2] (beta)
12- [Azure Application Gateway for Containers][27] (preview)
13- [BIG-IP Kubernetes Gateway][20] (beta)
14- [Cilium][16] (beta)
15- [Contour][3] (beta)
16- [Easegress][30] (beta)
17- [Emissary-Ingress (Ambassador API Gateway)][4] (alpha)
18- [Envoy Gateway][18] (beta)
19- [Flomesh Service Mesh][17] (beta)
20- [Gloo Edge 2.0][5] (work in progress)
21- [Google Kubernetes Engine][6] (GA)
22- [HAProxy Ingress][7] (alpha)
23- [HashiCorp Consul][8]
24- [Istio][9] (beta)
25- [Kong][10] (beta)
26- [Kuma][11] (beta)
27- [LiteSpeed Ingress Controller][19]
28- [NGINX Gateway Fabric][12]
29- [STUNner][21] (beta)
30- [Traefik][13] (alpha)
31- [Tyk][29] (work in progress)
32- [WSO2 APK][25] (GA)
33
34## Service Mesh Implementation Status <a name="meshes"></a>
35
36- [Istio][9] (experimental)
37- [Kuma][11] (experimental)
38- [Linkerd][28] (experimental)
39
40## Integrations <a name="integrations"></a>
41
42- [Flagger][14] (public preview)
43- [cert-manager][15] (alpha)
44- [argo-rollouts][22] (alpha)
45- [Knative][24] (alpha)
46- [Kuadrant][26] (work in progress)
47
48[1]:#acnodal-epic
49[2]:#apisix
50[3]:#contour
51[4]:#emissary-ingress-ambassador-api-gateway
52[5]:#gloo-edge
53[6]:#google-kubernetes-engine
54[7]:#haproxy-ingress
55[8]:#hashicorp-consul
56[9]:#istio
57[10]:#kong
58[11]:#kuma
59[12]:#nginx-gateway-fabric
60[13]:#traefik
61[14]:#flagger
62[15]:#cert-manager
63[16]:#cilium
64[17]:#flomesh-service-mesh-fsm
65[18]:#envoy-gateway
66[19]:#litespeed-ingress-controller
67[20]:#big-ip-kubernetes-gateway
68[21]:#stunner
69[22]:#argo-rollouts
70[23]:#amazon-elastic-kubernetes-service
71[24]:#knative
72[25]:#wso2-apk
73[26]:#kuadrant
74[27]:#azure-application-gateway-for-containers
75[28]:#linkerd
76[29]:#tyk
77[30]:#easegress
78
79[gamma]:/concepts/gamma/
80
81## Implementations
82
83In this section you will find specific links to blog posts, documentation and other Gateway API references for specific implementations.
84
85### Acnodal EPIC
86[EPIC][epic] is a Managed Application & API Gateway Service. The epic-controller installed in the cluster implements v1alpha2 and currently supports HTTPRoute. Defining Gateways and Routes creates a Gateway in the EPIC Service consisting of Envoy instances allocating public IP addresses and DNS for clients, and configures transport that sends request directly upstream to application endpoints in the cluster. EPIC is in public preview.
87
88Documentation can be found at [EPIC Application & API Gateway Service][epic]
89
90[epic]:https://www.epick8sgw.io
91
92### Amazon Elastic Kubernetes Service
93
94[Amazon Elastic Kubernetes Service (EKS)][eks] is a managed service that you can use to run Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane or nodes. EKS's implementation of the Gateway API is through [AWS Gateway API Controller][eks-gateway] which provisions [Amazon VPC Lattice][vpc-lattice] Resources for gateway(s), HTTPRoute(s) in EKS clusters.
95
96[eks]:https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html
97[eks-gateway]:https://github.com/aws/aws-application-networking-k8s
98[vpc-lattice]:https://aws.amazon.com/vpc/lattice/
99
100### APISIX
101
102[Apache APISIX][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.
103
104APISIX currently supports Gateway API `v1beta1` version of the specification for its [Apache APISIX Ingress Controller][apisix-1].
105
106[apisix]:https://apisix.apache.org/
107[apisix-1]:https://github.com/apache/apisix-ingress-controller
108
109### Azure Application Gateway for Containers
110
111[Application Gateway for Containers][azure-application-gateway-for-containers] is a managed application (layer 7) load balancing solution, providing dynamic traffic management capabilities for workloads running in a Kubernetes cluster in Azure. Follow the [quickstart guide][azure-application-gateway-for-containers-quickstart-controller] to deploy the ALB controller and get started with Gateway API.
112
113Application Gateway for Containers implements `v1beta1` specification of Gateway API.
114
115[azure-application-gateway-for-containers]:https://aka.ms/appgwcontainers/docs
116[azure-application-gateway-for-containers-quickstart-controller]:https://learn.microsoft.com/azure/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller
117
118### BIG-IP Kubernetes Gateway
119
120[BIG-IP Kubernetes Gateway][big-ip-kubernetes-gateway] is an open-source project that provides an implementation of the Gateway API using [F5 BIG-IP][f5bigip] as the data plane. It provides enterprises with high-performance Gateway API implementation.
121
122We are actively supporting various features of the Gateway API. For compatibility with the features of the Gateway API, please refer to [here][bigipgwfeatures]. For any questions about this project, welcome to create [Issues][bigipgwissues] or [PR][bigipgwpr]. Also, you are welcome to connect with us in the [slack channel][bigipgwslacklink].
123
124
125[big-ip-kubernetes-gateway]:https://gateway-api.f5se.io/
126[f5bigip]:https://f5.com
127[bigipgwfeatures]:https://github.com/f5devcentral/bigip-kubernetes-gateway/blob/master/docs/gateway-api-compatibility.md
128[bigipgwissues]:https://github.com/f5devcentral/bigip-kubernetes-gateway/issues
129[bigipgwpr]:https://github.com/f5devcentral/bigip-kubernetes-gateway/pulls
130[bigipgwslacklink]: https://gateway-api.f5se.io/Support-and-contact/
131
132### Cilium
133
134[](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v0.8.1/cilium-cilium.yaml)
135
136[Cilium][cilium] is an eBPF-based networking, observability and security
137solution for Kubernetes and other networking environments. It includes [Cilium
138Service Mesh][cilium-service-mesh], a highly efficient mesh data plane that can
139be run in [sidecarless mode][cilium-sidecarless] to dramatically improve
140performance, and avoid the operational complexity of sidecars. Cilium also
141supports the sidecar proxy model, offering choice to users. As of [Cilium 1.14][cilium114blog],
142Cilium supports Gateway API, passing conformance for v0.7.1.
143
144Cilium is open source and is a CNCF Graduates project.
145
146If you have questions about Cilium Service Mesh the #service-mesh channel on
147[Cilium Slack][cilium-slack] is a good place to start. For contributing to the development
148effort, check out the #development channel or join our [weekly developer meeting][cilium-meeting].
149
150[cilium]:https://cilium.io
151[cilium-service-mesh]:https://docs.cilium.io/en/stable/gettingstarted/#service-mesh
152[cilium-sidecarless]:https://isovalent.com/blog/post/cilium-service-mesh/
153[cilium114blog]:https://isovalent.com/blog/post/cilium-release-114/
154[cilium-slack]:https://cilium.io/slack
155[cilium-meeting]:https://github.com/cilium/cilium#weekly-developer-meeting
156
157### Contour
158
159[](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v0.8.0/projectcontour-contour.yaml)
160
161[Contour][contour] is a CNCF open source Envoy-based ingress controller for Kubernetes.
162
163Contour [v1.26.0][contour-release] implements Gateway API v0.8.0, supporting the v1alpha2 and v1beta1 API versions.
164All [Standard channel][contour-standard] resources (GatewayClass, Gateway, HTTPRoute, ReferenceGrant), plus TLSRoute, TCPRoute, and GRPCRoute, are supported.
165Contour's implementation passes all core and most extended Gateway API conformance tests included in the v0.8.0 release.
166
167See the [Contour Gateway API Guide][contour-guide] for information on how to deploy and use Contour's Gateway API implementation.
168
169For help and support with Contour's implementation, [create an issue][contour-issue-new] or ask for help in the [#contour channel on Kubernetes slack][contour-slack].
170
171_Some "extended" functionality is not implemented yet, [contributions welcome!][contour-contrib]._
172
173[contour]:https://projectcontour.io
174[contour-release]:https://github.com/projectcontour/contour/releases/tag/v1.26.0
175[contour-standard]:https://gateway-api.sigs.k8s.io/concepts/versioning/#release-channels-eg-experimental-standard
176[contour-guide]:https://projectcontour.io/docs/1.26/guides/gateway-api/
177[contour-issue-new]:https://github.com/projectcontour/contour/issues/new/choose
178[contour-slack]:https://kubernetes.slack.com/archives/C8XRH2R4J
179[contour-contrib]:https://github.com/projectcontour/contour/blob/main/CONTRIBUTING.md
180
181### Easegress
182
183[Easegress][easegress] is a Cloud Native traffic orchestration system.
184
185It can function as a sophisticated modern gateway, a robust distributed cluster, a flexible traffic orchestrator, or even an accessible service mesh.
186
187Easegress currently supports Gateway API `v1beta1` version of the specification by [GatewayController][easegress-gatewaycontroller].
188
189[easegress]:https://megaease.com/easegress/
190[easegress-gatewaycontroller]:https://github.com/megaease/easegress/blob/main/docs/04.Cloud-Native/4.2.Gateway-API.md
191
192### Emissary-Ingress (Ambassador API Gateway)
193
194[Emissary-Ingress][emissary] (formerly known as Ambassador API Gateway) is an open source CNCF project that
195provides an ingress controller and API gateway for Kubernetes built on top of [Envoy Proxy][envoy].
196See [here][emissary-gateway-api] for more details on using the Gateway API with Emissary.
197
198[emissary]:https://www.getambassador.io/docs/edge-stack
199[envoy]:https://envoyproxy.io
200[emissary-gateway-api]:https://www.getambassador.io/docs/edge-stack/latest/topics/using/gateway-api/
201
202### Envoy Gateway
203
204[](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v0.8.0/envoy-gateway.yaml)
205
206[Envoy Gateway][eg-home] is an [Envoy][envoy-org] subproject for managing Envoy-based application gateways. The supported
207APIs and fields of the Gateway API are outlined [here][eg-supported].
208Use the [quickstart][eg-quickstart] to get Envoy Gateway running with Gateway API in a
209few simple steps.
210
211[eg-home]:https://gateway.envoyproxy.io/
212[envoy-org]:https://github.com/envoyproxy
213[eg-supported]: https://gateway.envoyproxy.io/v0.5.0/user/gatewayapi-support.html
214[eg-quickstart]:https://gateway.envoyproxy.io/v0.5.0/user/quickstart.html
215
216### Flomesh Service Mesh (FSM)
217
218[Flomesh Service Mesh][fsm] is a community driven lightweight service mesh for Kubernetes East-West and North-South traffic management. Flomesh uses [ebpf](https://www.kernel.org/doc/html/latest/bpf/index.html) for layer4 and [pipy](https://flomesh.io/pipy) proxy for layer7 traffic management. Flomesh comes bundled with a load balancer, cross-cluster service registration/discovery and it supports multi-cluster networking. It supports `Ingress` (and as such is an "Ingress controller") and Gateway API.
219
220FSM support of Gateway API is built on top [Flomesh Gateway API](fgw) and it currently supports Kubernetes Gateway API version [v0.7.1](https://github.com/kubernetes-sigs/gateway-api/releases/tag/v0.7.1) with support for `v0.8.0` currently in progress.
221
222- [FSM Kubernetes Gateway API compatibility matrix](https://github.com/flomesh-io/fsm/blob/main/docs/gateway-api-compatibility.md)
223- [How to use Gateway API support in FSM](https://github.com/flomesh-io/fsm/blob/main/docs/tests/gateway-api/README.md)
224
225[fsm]:https://github.com/flomesh-io/fsm
226[flomesh]:https://flomesh.io
227[fgw]:https://github.com/flomesh-io/fgw
228
229### Gloo Edge
230
231Gloo Edge 2.0 is an Istio-native, fully-featured Envoy based API gateway that brings [Gloo Edge][glooedge] functionality to Istio. The [Solo.io][solo] team is actively working towards an implementation of the Gateway API.
232
233[glooedge]:https://docs.solo.io/gloo-edge/
234[solo]:https://www.solo.io
235
236### Google Kubernetes Engine
237
238[Google Kubernetes Engine (GKE)][gke] is a managed Kubernetes platform offered
239by Google Cloud. GKE's implementation of the Gateway API is through the [GKE
240Gateway controller][gke-gateway] which provisions Google Cloud Load Balancers
241for Pods in GKE clusters.
242
243The GKE Gateway controller supports weighted traffic splitting, mirroring,
244advanced routing, multi-cluster load balancing and more. See the docs to deploy
245[private or public Gateways][gke-gateway-deploy] and also [multi-cluster
246Gateways][gke-multi-cluster-gateway].
247
248[gke]:https://cloud.google.com/kubernetes-engine
249[gke-gateway]:https://cloud.google.com/kubernetes-engine/docs/concepts/gateway-api
250[gke-gateway-deploy]:https://cloud.google.com/kubernetes-engine/docs/how-to/deploying-gateways
251[gke-multi-cluster-gateway]:https://cloud.google.com/kubernetes-engine/docs/how-to/deploying-multi-cluster-gateways
252
253### HAProxy Ingress
254
255[HAProxy Ingress][h1] is a community driven ingress controller implementation for HAProxy.
256
257HAProxy Ingress v0.13 partially supports the Gateway API's v1alpha1 specification. See the [controller's Gateway API documentation][h2] to get informed about conformance and roadmap.
258
259[h1]:https://haproxy-ingress.github.io/
260[h2]:https://haproxy-ingress.github.io/docs/configuration/gateway-api/
261
262### HashiCorp Consul
263
264[Consul][consul], by [HashiCorp][hashicorp], is an open source control plane for multi-cloud networking. A single Consul deployment can span bare metal, VM and container environments.
265
266Consul service mesh works on any Kubernetes distribution, connects multiple clusters, and Consul CRDs provide a Kubernetes native workflow to manage traffic patterns and permissions in the mesh. [Consul API Gateway][consul-api-gw-doocs] supports Gateway API for managing North-South traffic.
267
268Please see the [Consul API Gateway documentation][consul-api-gw-doocs] for current information on the supported version and features of the Gateway API.
269
270[consul]:https://consul.io
271[consul-api-gw-doocs]:https://www.consul.io/docs/api-gateway
272[hashicorp]:https://www.hashicorp.com
273
274### Istio
275
276[](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v0.7.1/istio.io-istio.yaml)
277
278[Istio][istio] is an open source [service mesh][istio-mesh] and gateway implementation.
279
280A light-weight minimal install of Istio can be used to provide a Beta-quality
281implementation of the Kubernetes Gateway API for cluster ingress traffic
282control. For service mesh users, Istio 1.16 and later support the [GAMMA
283initiative's][gamma] experimental Gateway API [support for east-west traffic
284management][gamma] within the mesh.
285
286Much of Istio's documentation, including all of the [ingress tasks][istio-1] and several mesh-internal traffic management tasks, already includes parallel instructions for
287configuring traffic using either the Gateway API or the Istio configuration API.
288Check out the [Gateway API task][istio-2] for more information about the Gateway API implementation in Istio.
289
290[istio]:https://istio.io
291[istio-mesh]:https://istio.io/latest/docs/concepts/what-is-istio/#what-is-a-service-mesh
292[istio-1]:https://istio.io/latest/docs/tasks/traffic-management/ingress/
293[istio-2]:https://istio.io/latest/docs/tasks/traffic-management/ingress/gateway-api/
294
295### Kong
296
297[](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v0.8.1/kong-kubernetes-ingress-controller.yaml)
298
299[Kong][kong] is an open source API Gateway built for hybrid and multi-cloud environments.
300
301Kong supports Gateway API in the [Kong Kubernetes Ingress Controller (KIC)][kic], see the [Gateway API Guide][kong-gw-guide] for usage information.
302
303Kong also supports Gateway API in the [Kong Gateway Operator][kgo].
304
305For help and support with Kong's implementations please feel free to [create an issue][kong-issue-new] or a [discussion][kong-disc-new]. You can also ask for help in the [#kong channel on Kubernetes slack][kong-slack].
306
307[kong]:https://konghq.com
308[kic]:https://github.com/kong/kubernetes-ingress-controller
309[kong-gw-guide]:https://docs.konghq.com/kubernetes-ingress-controller/latest/guides/using-gateway-api/
310[kgo]:https://docs.konghq.com/gateway-operator/latest/
311[kong-issue-new]:https://github.com/Kong/kubernetes-ingress-controller/issues/new
312[kong-disc-new]:https://github.com/Kong/kubernetes-ingress-controller/discussions/new
313[kong-slack]:https://kubernetes.slack.com/archives/CDCA87FRD
314
315### Kuma
316
317[](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v0.8.0/kumahq-kuma.yaml)
318
319[Kuma][kuma] is an open source service mesh.
320
321Kuma implements the Gateway API specification for the Kuma built-in, Envoy-based Gateway with a beta stability guarantee. Check the [Gateway API Documentation][kuma-1] for information on how to setup a Kuma built-in gateway using the Gateway API.
322
323Kuma 2.3 and later support the [GAMMA initiative's][gamma] experimental
324Gateway API [support for east-west traffic management][gamma] within the mesh.
325
326[kuma]:https://kuma.io
327[kuma-1]:https://kuma.io/docs/latest/explore/gateway-api/
328
329### Linkerd
330
331[Linkerd][linkerd] is the first CNCF graduated [service mesh][linkerd-mesh].
332It is the only major mesh not based on Envoy, instead relying on a
333purpose-built Rust micro-proxy to bring security, observability, and
334reliability to Kubernetes, without the complexity.
335
336Linkerd 2.14 and later support the [GAMMA initiative's][gamma] experimental
337Gateway API [support for east-west traffic management][gamma] within the mesh.
338
339[linkerd]:https://linkerd.io/
340[linkerd-mesh]:https://buoyant.io/service-mesh-manifesto
341
342### LiteSpeed Ingress Controller
343
344The [LiteSpeed Ingress Controller](https://litespeedtech.com/products/litespeed-web-adc/features/litespeed-ingress-controller) uses the LiteSpeed WebADC controller to operate as an Ingress Controller and Load Balancer to manage your traffic on your Kubernetes cluster. It implements the full core Gateway API including Gateway, GatewayClass, HTTPRoute and ReferenceGrant and the Gateway functions of cert-manager. Gateway is fully integrated into the LiteSpeed Ingress Controller.
345
346- [Product documentation](https://docs.litespeedtech.com/cloud/kubernetes/).
347- [Gateway specific documentation](https://docs.litespeedtech.com/cloud/kubernetes/gateway).
348- Full support is available on the [LiteSpeed support web site](https://www.litespeedtech.com/support).
349
350### NGINX Gateway Fabric
351
352[](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v0.8.1/nginxinc-nginx-gateway-fabric.yaml)
353
354[NGINX Gateway Fabric][nginx-gateway-fabric] is an open-source project that provides an implementation of the Gateway API using [NGINX][nginx] as the data plane. The goal of this project is to implement the core Gateway API -- Gateway, GatewayClass, HTTPRoute, TCPRoute, TLSRoute, and UDPRoute -- to configure an HTTP or TCP/UDP load balancer, reverse-proxy, or API gateway for applications running on Kubernetes. NGINX Gateway Fabric is currently under development and supports a subset of the Gateway API.
355
356If you have any suggestions or experience issues with NGINX Gateway Fabric, please [create an issue][nginx-issue-new] or a [discussion][nginx-disc-new] on GitHub. You can also ask for help in the [#nginx-gateway-fabric channel on NGINX slack][nginx-slack].
357
358[nginx-gateway-fabric]:https://github.com/nginxinc/nginx-gateway-fabric
359[nginx]:https://nginx.org/
360[nginx-issue-new]:https://github.com/nginxinc/nginx-gateway-fabric/issues/new
361[nginx-disc-new]:https://github.com/nginxinc/nginx-gateway-fabric/discussions/new
362[nginx-slack]:https://nginxcommunity.slack.com/channels/nginx-gateway-fabric
363
364### STUNner
365
366[STUNner][stunner] is an open source cloud-native WebRTC media gateway for Kubernetes. STUNner is purposed specifically to facilitate the seamless ingestion of WebRTC media streams into a Kubernetes cluster, with simplified NAT traversal and dynamic media routing. Meanwhile, STUNner provides improved security and monitoring for large-scale real-time communications services. The STUNner dataplane exposes a standards compliant TURN service to WebRTC clients, while the control plane supports a subset of the Gateway API.
367
368STUNner currently supports version `v1alpha2` of the Gateway API specification. Check the [install guide][stunner-1] for information on how to deploy and use STUNner for WebRTC media ingestion. Please direct all questions, comments and bug-reports related to STUNner to the [STUNner project][stunner].
369
370[stunner]:https://github.com/l7mp/stunner
371[stunner-1]:https://github.com/l7mp/stunner/blob/main/doc/INSTALL.md
372
373### Traefik
374
375[Traefik][traefik] is an open source cloud-native application proxy.
376
377Traefik currently supports version `v1alpha2` (`v0.4.x`) of the Gateway API specification, check the [Kubernetes Gateway Documentation][traefik-1] for information on how to deploy and use Traefik's Gateway implementation.
378
379Traefik is currently working on implementing UDP, and ReferenceGrant. Status updates and documentation will be provided here as the work progresses.
380
381[traefik]:https://traefik.io
382[traefik-1]:https://doc.traefik.io/traefik/routing/providers/kubernetes-gateway/
383
384### Tyk
385
386[Tyk Gateway][tyk-gateway] is a cloud-native, open source, API Gateway.
387
388The [Tyk.io][tyk] team is working towards an implementation of the Gateway API. You can track progress of this project [here][tyk-operator].
389
390[tyk]:https://tyk.io
391[tyk-gateway]:https://github.com/TykTechnologies/tyk
392[tyk-operator]:https://github.com/TykTechnologies/tyk-operator
393
394### WSO2 APK
395
396[WSO2 APK][wso2-apk] is a purpose-built API management solution tailored for Kubernetes environments, delivering seamless integration, flexibility, and scalability to organizations in managing their APIs.
397
398WSO2 APK implements the Gateway API, encompassing Gateway and HTTPRoute functionalities. Additionally, it provides support for rate limiting, authentication/authorization, and analytics/observability through the use of Custom Resources (CRs).
399
400For up-to-date information on the supported version and features of the Gateway API, please refer to the [APK Gateway documentation][apk-doc]. If you have any questions or would like to contribute, feel free to create [issues or pull requests][repo]. Join our [Discord channel][discord] to connect with us and engage in discussions.
401
402[wso2-apk]:https://apk.docs.wso2.com/en/latest/
403[apk-doc]:https://apk.docs.wso2.com/en/latest/catalogs/kubernetes-crds/
404[repo]:https://github.com/wso2/apk
405[discord]:https://discord.com/channels/955510916064092180/1113056079501332541
406
407## Integrations
408
409In this section you will find specific links to blog posts, documentation and other Gateway API references for specific integrations.
410
411### Flagger
412
413[Flagger][flagger] is a progressive delivery tool that automates the release process for applications running on Kubernetes.
414
415Flagger can be used to automate canary deployments and A/B testing using Gateway API. It supports both the `v1alpha2` and `v1beta1` spec of Gateway API. You can refer to [this tutorial][flagger-tutorial] to use Flagger with any implementation of Gateway API.
416
417[flagger]:https://flagger.app
418[flagger-tutorial]:https://docs.flagger.app/tutorials/gatewayapi-progressive-delivery
419
420### cert-manager
421
422[cert-manager][cert-manager] is a tool to automate certificate management in cloud native environments.
423
424cert-manager can generate TLS certificates for Gateway resources. This is configured by adding annotations to a Gateway. It currently supports the `v1alpha2` spec of Gateway API. You can refer to the [cert-manager docs][cert-manager-docs] to try it out.
425
426[cert-manager]:https://cert-manager.io/
427[cert-manager-docs]:https://cert-manager.io/docs/usage/gateway/
428
429### Argo rollouts
430
431[Argo Rollouts][argo-rollouts] is a progressive delivery controller for Kubernetes. It supports several advanced deployment methods such as blue/green and canaries. Argo Rollouts supports the Gateway API via [a plugin][argo-rollouts-plugin].
432
433[argo-rollouts]:https://argo-rollouts.readthedocs.io/en/stable/
434[argo-rollouts-plugin]:https://github.com/argoproj-labs/rollouts-gatewayapi-trafficrouter-plugin/
435
436### Knative
437
438[Knative][knative] is a serverless platform built on Kubernetes. Knative Serving provides a simple API for running stateless containers with automatic management of URLs, traffic splitting between revisions, request-based autoscaling (including scale to zero), and automatic TLS provisioning. Knative Serving supports multiple HTTP routers through a plugin architecture, including a [gateway API plugin][knative-net-gateway-api] which is currently in alpha as not all Knative features are supported.
439
440[knative]:https://knative.dev/
441[knative-net-gateway-api]:https://github.com/knative-sandbox/net-gateway-api
442
443### Kuadrant
444
445[Kuadrant][kuadrant] is an open source multi cluster Gateway API controller that integrates with and provides policies to other Gateway API providers.
446
447Kuadrant supports Gateway API for defining gateways centrally and attaching policies such as DNS, TLS, Auth and Rate Limiting that apply to all gateway instances in a multi cluster environment.
448Kuadrant works with Istio as the underlying gateway provider, with plans to work with other gateway providers such as Envoy Gateway.
449
450For help and support with Kuadrant's implementation please feel free to [create an issue][kuadrant-issue-new] or ask for help in the [#kuadrant channel on Kubernetes slack][kuadrant-slack].
451
452[kuadrant]:https://kuadrant.io/
453[kuadrant-issue-new]:https://github.com/Kuadrant/multicluster-gateway-controller/issues/new
454[kuadrant-slack]:https://kubernetes.slack.com/archives/C05J0D0V525
View as plain text