Hi guys, So I have deployed and hosted deafult air...
# replication-troubleshooting
b
Hi guys, So I have deployed and hosted deafult airbyte instance on GKE using helm install. but now I wish to add my custom connector docker image hosted on Artifact registry to that cluster. How do I go about doing this?
t
you can do it but i’m almost sure that you won’t be able to use it after thar
we also have images hosted on artifact registry for the helm chart
but the connector images are pulled from public repo
when you click on “new source” you will never see your custom connector
it’s not in the official list of available connectors
so it won’t work
b
ah okay so are u saying that we cant export our manual custom connectors to Airbyte deployed using helm on GKE
like we'll only be able to use the official list of connectors? Thats it
t
yes
its their philosophy they want people to develop connectors open source for everyone
e
Not true. You can definitely add custom connectors. The image name (I believe that's what the param is called) in the UI is just the URL to the image in artifact repo. And then as long as GKE has access to artifact repo, then it should work. Just a little caveat, I don't have the exact same setup as you, but relatively similar. I have Airbyte running in EKS in AWS and a custom connector docker image in ECR that I use. Works just fine. Here's some info: https://airbytehq.github.io/operator-guides/using-custom-connectors/
🙏 1
t
o thats great i never heard it was possible
b
Perfect. Thanks for it I'll try this. I though it wont connect to other external repositories. but i guess Airbyte can handle that itself. Also I checked the new Airbyte version has some problem with displaying custom connectors so better to tuse an older version like 0.40.18 or older