Before you begin

Make sure that you have the following setup:

  • A connected device that can pull the required images from the internet.
  • An air-gapped or disconnected device that you want to install Gloo Gateway in.
  • A private image registry, such as Sonatype Nexus Repository or JFrog Artifactory that both the connected and disconnected devices can connect to.

Install Gloo Gateway

  1. Set the Gloo Gateway version that you want to install as an environment variable, such as the latest version in the following example.

      export GLOO_EE_VERSION=1.17.4

  2. On the connected device, download the Gloo Gateway Enterprise images.

      helm template glooe/gloo-ee --version $GLOO_EE_VERSION --set-string license_key=$GLOO_GATEWAY_LICENSE_KEY | yq e '. | .. | select(has("image"))' - | grep image: | sed 's/image: //'

    Example output for version 1.17.4:

      
   quay.io/solo-io/gloo-fed-apiserver:1.17.4@sha256:44a7bf678d6ddbf9953b33a974e4630adb9b9f7dc7ea9f6ee0b8a9fafebef212
   quay.io/solo-io/gloo-federation-console:1.17.4@sha256:b5b7b1697e2bd2b6f648fc1e5c76462626f774e0f1faa27a7c2f1fc19db0a6ea
   quay.io/solo-io/gloo-fed-apiserver-envoy:1.17.4@sha256:cc8cf1b71fff18394c063f583f75a05e29cfaa278532021c7d3f84e58f59eeeb
   quay.io/solo-io/gloo-fed:1.17.4@sha256:3db8fbf02ffdfc052ffe55fb82845b5d3560c62a6723688e780236ab8fa9f601
   quay.io/solo-io/gloo-ee:1.17.4@sha256:de044204d54bbd9c3a79fc890b6fdfeeb9b242b5e01af30c6f51146d1004be97
   quay.io/solo-io/discovery-ee:1.17.4@sha256:cb813c62574ec45939255c0ce50a5995c752085d2bbb8fdd26d9662fcc5f2841
   quay.io/solo-io/gloo-ee-envoy-wrapper:1.17.4@sha256:92bc7b6bf04dd7921a797c236f6dd12181caf513aacd87e752a8837a3ae1d1c8
   "docker.io/grafana/grafana:10.4.1"
   registry.k8s.io/kube-state-metrics/kube-state-metrics:v2.12.0
   "quay.io/prometheus-operator/prometheus-config-reloader:v0.73.2"
   "quay.io/prometheus/prometheus:v2.52.0"
   docker.io/busybox:1.28
   docker.io/redis:7.2.4-alpine
   quay.io/solo-io/rate-limit-ee:1.17.4@sha256:2f8e7c4f3288e76c5d0756cc7d9102e774a5f99228d05e03a996b0be9b7d547b
   quay.io/solo-io/extauth-ee:1.17.4@sha256:fefe0b13a11e8e38d89f20e59e559719a9ca0de80a1527379fa2f3f975f39c2e
   quay.io/solo-io/observability-ee:1.17.4@sha256:ffb2cb8b3357dba329caa132dab8114556a16a20072d8896010a89b5dc215775
   quay.io/solo-io/kubectl:1.17.16@sha256:7de9f55baa7364e2c45139b67c3a0ae1b83ab3bbb201a5fe1ef3d21e0a1ac4fa
   quay.io/solo-io/kubectl:1.17.16@sha256:7de9f55baa7364e2c45139b67c3a0ae1b83ab3bbb201a5fe1ef3d21e0a1ac4fa
   quay.io/solo-io/kubectl:1.17.16@sha256:7de9f55baa7364e2c45139b67c3a0ae1b83ab3bbb201a5fe1ef3d21e0a1ac4fa
   quay.io/solo-io/kubectl:1.17.16@sha256:7de9f55baa7364e2c45139b67c3a0ae1b83ab3bbb201a5fe1ef3d21e0a1ac4fa
   quay.io/solo-io/kubectl:1.17.16@sha256:7de9f55baa7364e2c45139b67c3a0ae1b83ab3bbb201a5fe1ef3d21e0a1ac4fa
   quay.io/solo-io/certgen:1.17.16@sha256:23b64858cb10d6f6f6eaaa477a9306d4840361436481d0adb5d43048dad80e4d
   docker.io/alpine/k8s:1.29.2

  3. Push the images from the connected device to a private registry that the disconnected device can pull the images from. For instructions and any credentials you must set up to complete this step, consult your registry provider, such as Nexus Repository Manager or JFrog Artifactory.

  4. Optional: You might want to set up your private registry so that you can also pull the Helm charts. For instructions, consult your registry provider, such as Nexus Repository Manager or JFrog Artifactory.

  5. Install Gloo Gateway. Make sure to define the downloaded images in your Helm values file. For more information, see the Helm reference.