From 205d0c893c07c9d2ab5182781748e48a6a023736 Mon Sep 17 00:00:00 2001 From: "alexandre.gervais" Date: Wed, 23 Jan 2019 12:32:09 -0500 Subject: [PATCH] Add Ambassador in list of ingress controller solutions --- content/en/docs/concepts/services-networking/ingress.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md index d5d2de00efcc6..94ef01c7f3d2a 100644 --- a/content/en/docs/concepts/services-networking/ingress.md +++ b/content/en/docs/concepts/services-networking/ingress.md @@ -64,6 +64,9 @@ In order for the ingress resource to work, the cluster must have an ingress cont Additional controllers include: +* [Ambassador](https://www.getambassador.io/) API Gateway is an [Envoy](https://www.envoyproxy.io) based ingress + controller with [community](https://www.getambassador.io/docs) or + [commercial](https://www.getambassador.io/pro/) support from [Datawire](https://www.datawire.io/). * [Contour](https://github.com/heptio/contour) is an [Envoy](https://www.envoyproxy.io) based ingress controller provided and supported by Heptio. * F5 Networks provides [support and maintenance](https://support.f5.com/csp/article/K86859508)