Is anyone ran airbyte in airgapped environment by ...
# airbyte-agents-ask-ai
j
Is anyone ran airbyte in airgapped environment by putting airbyte repo in gitlab and github container registry ?
k
Yes, running Airbyte in an air-gapped environment using a private container registry (like GitHub Container Registry or GitLab's registry) is a supported approach. Here's how it works: Using a Custom Image Registry for Air-Gapped Airbyte Step 1: Get the list of all required Airbyte images
Copy code
abctl images manifest
This outputs all platform images you need to mirror. [Custom Image Registry] Step 2: Tag and push images to your registry For GitHub Container Registry (ghcr.io):
Copy code
abctl images manifest | xargs -L1 -I{} docker tag {} ghcr.io/NAMESPACE/{} && docker push ghcr.io/NAMESPACE/{}
For connector images, pull, tag, and push individually before adding sources/destinations:
Copy code
docker pull airbyte/destination-google-sheets:latest
docker tag airbyte/destination-google-sheets:latest ghcr.io/NAMESPACE/destination-google-sheets:latest
docker push ghcr.io/NAMESPACE/destination-google-sheets:latest
[Tag and Push Images] Step 3: Configure Airbyte to use your registry In your `values.yaml`:
Copy code
global:
  image:
    registry: ghcr.io/NAMESPACE
If authentication is required, create a Kubernetes secret and reference it:
Copy code
kubectl create secret generic regcred \
--from-file=.dockerconfigjson=<path/to/.docker/config.json> \
--type=kubernetes.io/dockerconfigjson
Copy code
global:
  image:
    registry: ghcr.io/NAMESPACE
  imagePullSecrets:
    - name: regcred
[Step 1: Customize Registry] âš ī¸ Known Caveat: Connector Registry Fetching Even with images mirrored, Airbyte's bootloader may still try to fetch connector definitions from a remote registry (e.g.,
raw.githubusercontent.com
). This is a known issue in air-gapped setups. [GitHub Issue] Some users have worked around this by configuring a proxy or whitelisting the
airbyte.com
domain. Additionally, for local installs (
abctl
), you can install from a local Helm chart directory to avoid internet access:
Copy code
abctl local install --chart ./path/to/local/airbyte-chart
[abctl Local Install] In summary, mirroring images to GitHub Container Registry or GitLab's registry is the recommended approach, but be aware that full air-gapping may require additional steps to handle remote connector definition fetching. 👍 0 button 👎 0 button â„šī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.