Hi, does anyone know how I can point to a private ...
# ask-community-for-troubleshooting
r
Hi, does anyone know how I can point to a private registry when adding a connector? (deployment: K8s/ helm chart -- 0.33.7-alpha)
1
j
I'm afraid that's not possible since we need to
docker login
first. The UI only let's you enter a URI
👍 1
r
I'm unable to reference public repositories in my cluster. How would you recommend I manage connectors?
j
I am able to do that. We deploy them to AWS ECR Public and use the URI from there. Example: public.ecr.aws/<repo-id>/<image-name>
make sure your cluster has public internet access, if you place them in a private subnet, it needs to have a NAT gateway
r
Awesome, how would you specify documentation URL in this case?
j
I suppose this might vary depending on the registry you use. For AWS ECR, there’s an option to add about and usage details for a image and that links to
<https://gallery.ecr.aws/<repo-id>/<image-name>>
r
Great thanks so much, so if I have a "public" registry inside of the subnet, this method would work ok as well?
j
That is correct. If the cluster is inside a private subnet, it can access anything from the internet given it has a NAT gateway. Subnets confuse me as well, so made these notes: https://github.com/jagannathsrs/notes/blob/main/aws-networking.md Hope these come in handy!
👍 1
r
Sorry I meant if the registry (which requires no login) is inside of the subnet, this method also works?
j
would this registry have a public IP or a private IP? either way I think it will work if it doesn’t require login, just make sure it is reachable from the Airbyte instance
👍 1
r
Thanks for your help, really appreciate it
airbyte heart 1