Skip to content
An Envoy-Powered API Gateway
Branch: master
Clone or download
christian-posta and soloio-bulldozer Fix for #577 (#579)
* Fix for #577
* fixed up determining what to send back when not http/s
* remove ugly parens
* fixed formatting, changed shorthand params
* removed shorthand values for proxy command
* fix merge conflict with master
* added changelog
* bumped changelog version because of breaking change
Latest commit 91f800d Mar 21, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs Fix for #577 (#579) Mar 21, 2019
hack removed dependence on namespace from yaml (#424) Feb 20, 2019
install Glooctl uninstall (#580) Mar 21, 2019
projects Fix for #577 (#579) Mar 21, 2019
.gitattributes Migrate to hugo docs (#417) Feb 15, 2019
.gitignore Regression tests (#478) Mar 1, 2019
Gopkg.lock Update to new solo-kit, which changes rendering of anchor links (#586) Mar 21, 2019
LICENSE License (#494) Mar 5, 2019
Makefile SDS support for gloo (#559) Mar 19, 2019 Contributing (#492) Mar 5, 2019
cloudbuild-cache.yaml Ci checks (#327) Jan 24, 2019
cloudbuild-push-docs.yaml Fix push (#436) Feb 20, 2019

An Envoy-Powered API Gateway

Gloo is a feature-rich, Kubernetes-native ingress controller, and next-generation API gateway. Gloo is exceptional in its function-level routing; its support for legacy apps, microservices and serverless; its discovery capabilities; its numerous features; and its tight integration with leading open-source projects. Gloo is uniquely designed to support hybrid applications, in which multiple technologies, architectures, protocols, and clouds can coexist.

Installation   |   Documentation   |   Blog   |   Slack   |   Twitter

Gloo Architecture


Using Gloo

  • Kubernetes ingress controller: Gloo can function as a feature-rich ingress controller, built on top of the Envoy Proxy.
  • Next-generation API gateway : Gloo provides a long list of API gateway features, including rate limiting, circuit breaking, retries, caching, external authentication and authorization, transformation, service-mesh integration, and security.
  • Hybrid apps: Gloo creates applications that route to backends implemented as microservices, serverless functions, and legacy apps. This feature can help users to gradually migrate from their legacy code to microservices and serverless; can let users add new functionalities using cloud-native technologies while maintaining their legacy codebase; can be used in cases where different teams in an organization choose different architectures; and more. See here for more on the Hybrid App paradigm.

What makes Gloo unique

  • Function-level routing allows integration of legacy applications, microservices and serverless: Gloo can route requests directly to functions, which can be a serverless function call (e.g. Lambda, Google Cloud Function, OpenFaaS function, etc.), an API call on a microservice or a legacy service (e.g. a REST API call, OpenAPI operation, XML/SOAP request etc.), or publishing to a message queue (e.g. NATS, AMQP, etc.). This unique ability is what makes Gloo the only API gateway that supports hybrid apps, as well as the only one that does not tie the user to a specific paradigm.
  • Gloo incorporates vetted open-source projects to provide broad functionality: Gloo support high-quality features by integrating with top open-source projects, including gRPC, GraphQL, OpenTracing, NATS and more. Gloo's architecture allows rapid integration of future popular open-source projects as they emerge.
  • Full automated discovery lets users move fast: Upon launch, Gloo creates a catalog of all available destinations, and continuously maintains it up to date. This takes the responsibility for 'bookkeeping' away from the developers, and guarantees that new feature become available as soon as they are ready. Gloo discovers across IaaS, PaaS and FaaS providers, as well as Swagger, gRPC, and GraphQL.
  • Gloo integrates intimately with the user's environment: with Gloo, users are free to choose their favorite tools for scheduling (such as K8s, Nomad, OpenShift, etc), persistence (K8s, Consul, etcd, etc) and security (K8s, Vault).

Next Steps


Gloo would not be possible without the valuable open-source work of projects in the community. We would like to extend a special thank-you to Envoy.

You can’t perform that action at this time.