From 1eae4bfb3e2417cb5fd08de270fc2fc61b57ac86 Mon Sep 17 00:00:00 2001 From: Christian Posta Date: Wed, 23 Jan 2019 10:39:59 -0700 Subject: [PATCH] Added Gloo as an example of an ingress controller (#12218) * Added Gloo as an example of an ingress controller * put in alphabetical order --- content/en/docs/concepts/services-networking/ingress.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md index d5d2de00ef..069f780aff 100644 --- a/content/en/docs/concepts/services-networking/ingress.md +++ b/content/en/docs/concepts/services-networking/ingress.md @@ -68,6 +68,7 @@ Additional controllers include: provided and supported by Heptio. * F5 Networks provides [support and maintenance](https://support.f5.com/csp/article/K86859508) for the [F5 BIG-IP Controller for Kubernetes](http://clouddocs.f5.com/products/connectors/k8s-bigip-ctlr/latest). +* [Gloo](https://gloo.solo.io) is an open-source ingress controller based on [Envoy](https://www.envoyproxy.io) which offers API Gateway functionality with enterprise support from [solo.io](https://www.solo.io). * [HAProxy](http://www.haproxy.org/) based ingress controller [jcmoraisjr/haproxy-ingress](https://github.com/jcmoraisjr/haproxy-ingress) which is mentioned on the blog post [HAProxy Ingress Controller for Kubernetes](https://www.haproxy.com/blog/haproxy_ingress_controller_for_kubernetes/).