Installing on Kubernetes

To install Gloo Enterprise you need a License Key. If you don’t have one, go to and request a trial now. Once you request a trial, an e-mail will be sent to you with your unique License Key that you will need as part of installing Gloo.

Each Key is valid for 31 days. You can request a new key if your current key has expired. The License Key is required only during the installation process. Once you install, a secret will be created to hold your unique key.

If this is your first time running Gloo, you’ll need to download the command-line interface (CLI) called glooctl onto your local machine. You’ll use this CLI to interact with Gloo, including installing it onto your Kubernetes cluster. Directions on installing glooctl are here.

Before starting installation, please ensure that you’ve prepared your Kubernetes cluster per the community Prep Kubernetes instructions.

Overall flow for installing

  1. Prepare Kubernetes Cluster
  2. Install Gloo Enterprise using CLI
  3. Verify installation

If for some reason you ever needed to uninstall Gloo, please follow these instructions

There are several options for deploying Gloo, depending on your use case and deployment platform.

  • Gateway: Gloo’s full feature set is available via its v1/Gateway API. The Gateway API is modeled on Envoy’s own API with the use of opinionated defaults to make complex configurations possible, while maintaining simplicity when required.

  • Ingress (Not currently supported): Gloo will support configuration the Kubernetes Ingress resource, acting as a Kubernetes Ingress Controller.

ingress objects must have the annotation "": "gloo" to be processed by the Gloo Ingress.

  • Knative (Not currently supported): Gloo will integrate automatically with Knative as a cluster-level ingress for Knative-Serving. Gloo can be used in this way as a lightweight replacement for Istio when using Knative-Serving.

If this process does not work, please open an issue. We are happy to answer questions on our diligently staffed Slack channel as well.

Install Gloo via Command Line Interface (CLI)

Choosing a deployment option for installing Gloo into your Kubernetes cluster:

Gloo Enterprise installation require you to use an extra --license-key YOUR_LICENSE_KEY with your license key you received either as part of your subscription or as part of a trial request from

You can install Gloo to an existing namespace by providing the -n option, e.g. glooctl install gateway -n my-namespace. If the option is not provided, the namespace defaults to gloo-system.

Install the Gloo Gateway

Once your Kubernetes cluster is up and running, run the following command to deploy the Gloo Gateway to the gloo-system namespace:

glooctl install gateway --license-key YOUR_LICENSE_KEY

After you verify your installation, please see Getting Started on Kubernetes to get started using the Gloo Gateway.

Install the Gloo Ingress Controller

Once your Kubernetes cluster is up and running, run the following command to deploy the Gloo Ingress to the gloo-system namespace:

glooctl install ingress --license-key YOUR_LICENSE_KEY

After you verify your installation, please see Getting Started with Kubernetes Ingress to get started using the Gloo Ingress Controller.

Install the Gloo Knative Cluster Ingress

Once your Kubernetes cluster is up and running, run the following command to deploy Knative-Serving components to the knative-serving namespace and Gloo to the gloo-system namespace:

glooctl install knative --license-key YOUR_LICENSE_KEY

After you verify your installation, please see Getting Started with Gloo and Knative to use Gloo as your Knative Ingress.

Verify your Installation

Check that the Gloo pods and services have been created. Depending on your install option, you may see some differences from the following example. And if you choose to install Gloo into a different namespace than the default gloo-system, then you will need to query your chosen namespace instead.

kubectl get all -n gloo-system
NAME                                                       READY   STATUS    RESTARTS   AGE
pod/api-server-56fcb78878-d9mxt                            2/2     Running   0          5m21s
pod/discovery-759bd6cf85-sphjb                             1/1     Running   0          5m22s
pod/extauth-679d587db8-l9k56                               1/1     Running   0          5m21s
pod/gateway-568bfd477c-487zw                               1/1     Running   0          5m22s
pod/gateway-proxy-c84cbd647-n9kz2                          1/1     Running   0          5m22s
pod/gloo-6979c5bd8-2dfrj                                   1/1     Running   0          5m22s
pod/glooe-grafana-86445b465b-mnn8t                         1/1     Running   0          5m22s
pod/glooe-prometheus-kube-state-metrics-8587f58df6-954pw   1/1     Running   0          5m22s
pod/glooe-prometheus-server-6bd6f4667d-zqffp               2/2     Running   0          5m21s
pod/observability-6db6c659dd-v4bkp                         1/1     Running   0          5m21s
pod/rate-limit-6b847b95c8-kwcbd                            1/1     Running   1          5m21s
pod/redis-7f6954b84d-ff4ck                                 1/1     Running   0          5m21s

NAME                                          TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
service/apiserver-ui                          NodePort   <none>        8088:31160/TCP               5m22s
service/extauth                               ClusterIP     <none>        8080/TCP                     5m22s
service/gateway-proxy                         LoadBalancer    <pending>     80:31627/TCP,443:30931/TCP   5m22s
service/gloo                                  ClusterIP     <none>        9977/TCP                     5m22s
service/glooe-grafana                         ClusterIP   <none>        80/TCP                       5m22s
service/glooe-prometheus-kube-state-metrics   ClusterIP      None             <none>        80/TCP                       5m22s
service/glooe-prometheus-server               ClusterIP   <none>        80/TCP                       5m22s
service/rate-limit                            ClusterIP    <none>        18081/TCP                    5m22s
service/redis                                 ClusterIP     <none>        6379/TCP                     5m22s

NAME                                                  READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/api-server                            1/1     1            1           5m21s
deployment.apps/discovery                             1/1     1            1           5m22s
deployment.apps/extauth                               1/1     1            1           5m21s
deployment.apps/gateway                               1/1     1            1           5m22s
deployment.apps/gateway-proxy                         1/1     1            1           5m22s
deployment.apps/gloo                                  1/1     1            1           5m22s
deployment.apps/glooe-grafana                         1/1     1            1           5m22s
deployment.apps/glooe-prometheus-kube-state-metrics   1/1     1            1           5m22s
deployment.apps/glooe-prometheus-server               1/1     1            1           5m22s
deployment.apps/observability                         1/1     1            1           5m21s
deployment.apps/rate-limit                            1/1     1            1           5m21s
deployment.apps/redis                                 1/1     1            1           5m21s

NAME                                                             DESIRED   CURRENT   READY   AGE
replicaset.apps/api-server-56fcb78878                            1         1         1       5m21s
replicaset.apps/discovery-759bd6cf85                             1         1         1       5m22s
replicaset.apps/extauth-679d587db8                               1         1         1       5m21s
replicaset.apps/gateway-568bfd477c                               1         1         1       5m22s
replicaset.apps/gateway-proxy-c84cbd647                          1         1         1       5m22s
replicaset.apps/gloo-6979c5bd8                                   1         1         1       5m22s
replicaset.apps/glooe-grafana-86445b465b                         1         1         1       5m22s
replicaset.apps/glooe-prometheus-kube-state-metrics-8587f58df6   1         1         1       5m22s
replicaset.apps/glooe-prometheus-server-6bd6f4667d               1         1         1       5m21s
replicaset.apps/observability-6db6c659dd                         1         1         1       5m21s
replicaset.apps/rate-limit-6b847b95c8                            1         1         1       5m21s
replicaset.apps/redis-7f6954b84d                                 1         1         1       5m21s

The Knative install option will also install Knative Serving components into the knative-service namespace.

kubectl get all -n knative-serving
NAME                              READY     STATUS    RESTARTS   AGE
pod/activator-5c8d977d45-6x9s4    1/1       Running   0          2m
pod/autoscaler-5cd4bb6dbc-kwt4q   1/1       Running   0          2m
pod/controller-66cd7d99df-c9fnx   1/1       Running   0          30s
pod/webhook-6d9568d-q27vv         1/1       Running   0          2m

NAME                        TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
service/activator-service   ClusterIP   <none>        80/TCP,9090/TCP     2m
service/autoscaler          ClusterIP    <none>        8080/TCP,9090/TCP   2m
service/controller          ClusterIP   <none>        9090/TCP            2m
service/webhook             ClusterIP   <none>        443/TCP             2m

NAME                         DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/activator    1         1         1            1           2m
deployment.apps/autoscaler   1         1         1            1           2m
deployment.apps/controller   1         1         1            1           2m
deployment.apps/webhook      1         1         1            1           2m

NAME                                    DESIRED   CURRENT   READY     AGE
replicaset.apps/activator-5c8d977d45    1         1         1         2m
replicaset.apps/autoscaler-5cd4bb6dbc   1         1         1         2m
replicaset.apps/controller-66cd7d99df   1         1         1         2m
replicaset.apps/webhook-6d9568d         1         1         1         2m

NAME                                                 AGE   2m       2m


To uninstall Gloo and all related components, simply run the following.

This will also remove Knative-Serving, if it was installed by glooctl.

glooctl uninstall

If you installed Gloo to a different namespace, you will have to specify that namespace using the -n option:

glooctl uninstall -n my-namespace

Next Steps

After you’ve installed Gloo, please check out our Basic Routing Guide with Gloo Enterprise Console and our User Guides.