Airgap environment

Install Gloo Gateway in an air-gapped environment, such as an on-premises datacenter, a cluster that is available on the intranet or private network only, or other disconnected environments.

This feature is an **Enterprise-only** feature that requires a Gloo Gateway Enterprise license.

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

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.21.0
```

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.21.0:



quay.io/solo-io/gloo-fed-apiserver:1.21.0-beta1@sha256:3cc015fd6d427adc6e17e954b35ff661dc45b6e5faabf612e55d1050ccd4c421
quay.io/solo-io/gloo-federation-console:1.21.0-beta1@sha256:faccac3c9cd39963371ee5885ae56d5e75e8072404ffdd067060a3216795f8e1
quay.io/solo-io/gloo-fed-apiserver-envoy:1.21.0-beta1@sha256:0f24f89fa9d18554cf88073f6bcbbc12b4e09feaf5f0aa1dd84cb067475fb31f
quay.io/solo-io/gloo-fed:1.21.0-beta1@sha256:607cd604c6f7a9677def8305fbf54470dbf9e7c12499363223daa48f1f77505d
quay.io/solo-io/gloo-ee:1.21.0-beta1@sha256:b14275a894cfea6b58ec35554c1bb3a73702e8aecc022d3badbc168a7d881997
quay.io/solo-io/gloo-ee-envoy-wrapper:1.21.0-beta1@sha256:9c6e8590517326176666bc4a57a4abf5bb768c32643d2bc2ed72c51ab26a5044
“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.11-alpine
quay.io/solo-io/rate-limit-ee:1.21.0-beta1@sha256:0bd4d19381f04773b0eb80506d0e5052dc76452c270d01595df1ccf53fe9b039
quay.io/solo-io/extauth-ee:1.21.0-beta1@sha256:4f8515b03960ea13ce02aeafb475d8c83db98c827840b1aff2246705f5046667
quay.io/solo-io/observability-ee:1.21.0-beta1@sha256:89e9e2d3faef337e95e8909b6684592b846384d87019eb79cc6df73b7cde4a71
quay.io/solo-io/kubectl:1.21.0-beta16@sha256:77d4483363f58941436dc07f94acc52b1bc751c18dd90a8dca38b7e7cbd2a0bb
quay.io/solo-io/kubectl:1.21.0-beta16@sha256:77d4483363f58941436dc07f94acc52b1bc751c18dd90a8dca38b7e7cbd2a0bb
quay.io/solo-io/kubectl:1.21.0-beta16@sha256:77d4483363f58941436dc07f94acc52b1bc751c18dd90a8dca38b7e7cbd2a0bb
quay.io/solo-io/kubectl:1.21.0-beta16@sha256:77d4483363f58941436dc07f94acc52b1bc751c18dd90a8dca38b7e7cbd2a0bb
quay.io/solo-io/kubectl:1.21.0-beta16@sha256:77d4483363f58941436dc07f94acc52b1bc751c18dd90a8dca38b7e7cbd2a0bb
quay.io/solo-io/certgen:1.21.0-beta16@sha256:d04eb6183b27a79cc226171743c8cd8978e1d91a0163df3212de00ed13b2f245
docker.io/alpine/k8s:1.29.2@sha256:a51aa37f0a34ff827c7f2f9cb7f6fbb8f0e290fa625341be14c2fcc4b1880f60

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.
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.
Install Gloo Gateway. Make sure to define the downloaded images in your Helm values file. For more information, see the Helm reference.

Helm Argo CD