Setup
Review the following setup paths for the open source and enterprise editions of Gloo Gateway.
Open Source
Gloo Gateway Open Source Software (OSS) runs in gateway or ingress modes to enable different use cases.
Note: The installation modes are not mutually exclusive. To run both gateway in and ingress modes of Gloo Gateway OSS, install separate instances of Gloo Gateway in the same or different namespaces.
|
Run Gloo Gateway in gateway mode to function as an API Gateway. This is the most fully-featured and customizable installation of Gloo Gateway, and is the recommended install for first-time users. Gloo Gateway can be configured via Kubernetes Custom Resources, Consul Key-Value storage, or .yaml files on Gloo Gateway's local filesystem.
|
|
Run Gloo Gateway in ingress mode to act as a standard Kubernetes Ingress controller. In this mode, Gloo Gateway will import its configuration from the networking.k8s.io/v1.Ingress Kubernetes resource. This can be used to achieve compatibility with the standard Kubernetes ingress API. Note that Gloo Gateway's Ingress API does not support customization via annotations. If you wish to extend Gloo Gateway beyond the functions of basic ingress, it is recommended to run Gloo Gateway in gateway mode.
|
Enterprise
Gloo Gateway Enterprise Edition (EE) has a single installation workflow.
To run the Enterprise Edition, you must install or upgrade Gloo Gateway with an enterprise license key. Contact your Solo Account Representative for a license key. To request a trial, fill out this request form and check Gloo Gateway. If your license key is expired, you can update the license key.
|
Gloo Gateway Enterprise is based on open-source Gloo Gateway with additional, closed source features. For a comparison between open source and enterprise editions, see the FAQs. For installation instructions, see the Enterprise setup guide. |