john roger
05/30/2026, 8:22 AMkapa.ai
05/30/2026, 8:22 AMabctl 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):
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:
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`:
global:
image:
registry: ghcr.io/NAMESPACE
If authentication is required, create a Kubernetes secret and reference it:
kubectl create secret generic regcred \
--from-file=.dockerconfigjson=<path/to/.docker/config.json> \
--type=kubernetes.io/dockerconfigjson
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:
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.