I am trying to get Airbyte working with a private docker registry. I was able to update the helm charts for all the images and get this working. I was able to update the JOB_KUBE_* environment variables to use the private registry for busybox/curl/socat. However, the only way I have found to fix the source/destination image locations is to overwrite the actor_definitions table in the database. This works for syncs that don't have normalization enable, however it seems that the image name is used as the lookup to check what type of normalization to use and this fails when the image names are overwritten in the database. All this seems kind of hacky and does not yet fully work so I am trying to just use the imageRegistry setting in the global area of the helm chart (thus maintaining the same image paths as in docker.io) but this does not seem to disseminate anywhere (tried for main worker/webapp/server images and busybox/curl/socat) especially down into the source and destination image locations. What are my options to get this to work other than forking the Java code?

@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2539 to ensure timely resolution!

Hey there, for connectors it is indeed very tricky - it is pretty amazing you have gotten so far. I'm not sure about

imageRegistry

, but our kubernetes deployments are still in alpha and need to be improved (if you have a moment please submit a Github issue requesting this functionality!) Instead of overwriting the built in connectors, it is possible to add the connector images from your private registry into Airbyte as custom connectors. This will probably run a lot more smoothly. There is more details on the process in this doc, along with info on required Kubernetes env config: https://docs.airbyte.com/operator-guides/using-custom-connectors/

Hi, Any solution found for this issue? I came to the impossibility of pulling images from docker repo due to pull rate limit, so having the option of specifying a private repo for all the images used by airbyte would be great!

Dana, today you must pull manually the images from your private registry. There isn’t an option to Airbyte make the call to another registry yet.

Thanks for those that chimed in! I do have this working using the patch the is forever sitting in the queue to be integrated. I just grabbed it and rebuilt and deployed. This is the change https://github.com/airbytehq/airbyte/pull/16969 but I had to make quite a few edits since it has gotten stale and the auto merging is broken.