Summary
The user is inquiring about configuring Airbyte to pull Docker images for connectors from a private proxy repository instead of the default Docker Hub. This involves modifications in the helm chart deployment, specifically within the values.yaml file to adjust image parameters for various components.
Question
Hi all, is it possible to pull the docker images used by a connection through a private proxy repository.
Let me explain.
I deployed airbyte using the helm chart (0.248.5).
Into values.yaml file, several images parameters can be defined to pull them from my private proxy repo like webapp, worker, jobs, …
However, when a connection is synchronizing, several pods are created, source|destination-connector-check, source|destination-connector-read|write, orchestrator-repl…
These docker images are pulled from http://docker.io|docker.io and their version depends on the configuration.
Can I configure airbyre to pull source-s3 from private-proxy-repo/airbyte/source-s3 instead of http://docker.io/airbyte/source-s3|docker.io/airbyte/source-s3??
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.