Setup

Gloo Edge Open-Source

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

Run Gloo Edge in gateway mode to function as an API Gateway. This is the most fully-featured and customizable installation of Gloo Edge, and is our recommended install for first-time users. Gloo Edge can be configured via Kubernetes Custom Resources, Consul Key-Value storage, or .yaml files on Gloo Edge's local filesystem.
Run Gloo Edge in knative mode to serve as the Gateway/Ingress for Knative, configured automatically by Knative Serving to route to Knative Services.
Run Gloo Edge in ingress mode to act as a standard Kubernetes Ingress controller. In this mode, Gloo Edge 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 Edge's Ingress API does not support customization via annotations. If you wish to extend Gloo Edge beyond the functions of basic ingress, it is recommended to run Gloo Edge 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 Edge Enterprise

Gloo Edge Enterprise has a single installation workflow:

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