Gloo Open-Source

Gloo Open-Source runs in 3 different modes to enable different use cases:

Run Gloo in gateway mode to function as an API Gateway. This is the most fully-featured and customizable installation of Gloo, and is our recommended install for first-time users. The Gloo Gateway can be configured via Kubernetes Custom Resources, Consul Key-Value storage, or .yaml files on Gloo's local filesystem.
Run Gloo in knative mode to serve as the Gateway/Ingress for Knative, configured automatically by Knative Serving to route to Knative Services.
Run Gloo in ingress mode to act as a standard Kubernetes Ingress controller. In this mode, Gloo will import its configuration from the extensions/v1beta1.Ingress Kubernetes resource. This can be used to achieve compatibility with the standard Kubernetes ingress API. Note that Gloo's Ingress API does not support customization via annotations. If you wish to extend Gloo beyond the functions of basic ingress, it is recommended to run Gloo in gateway mode.

Note: The installation modes are not mutually exclusive, e.g. if you wish to run gateway in conjunction with ingress, it can be done by installing both options to the same (or different) namespaces.

Gloo Enterprise

Gloo Enterprise has a single installation workflow:

Gloo Enterprise is based on the open-source Gloo Gateway with additional (closed source) UI and plugins. See the Gloo Enterprise documentation for more details on the additional features of the Enterprise version of Gloo.