Inquiring about the backward compatibility of Docker images with Airbyte 1.0
Hi,
I have several docker image working fine with older version of Airbyte(Before 1.0). When I add them to Airbyte 1.0, it can’t be added in the UI and hangs. Is Airbyte 1.0 backward compatible?
Thanks!
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.
I haven’t noticed any issues with custom connectors I created 5 months ago. They work just fine on Airbyte 1.0.0. Maybe you need to debug your setup.
follow-up question, if i will push the image to artifact registry
what will be the difference
since it will be in kind
how did you add the image to airbyte 1.0? did you store the image to a repository then just add them in the ui of airbye 1.0?
it depends on deployment,
for EKS + helm chart, I store Docker image in ECR
for abctl, I load Docker image into kind cluster
in both cases I go to Settings → Sources (or Destinations) → New connector → Add a new Docker connector
the docker image is at this directory…airbyte/connector-name
this is local installation
you have to build Docker image for your connector if you are using custom one, then load into kind cluster
https://docs.airbyte.com/operator-guides/using-custom-connectors/#loading-connector-docker-containers-into-kind
in your case:
kind load docker-image airbyte/source-dot-fmcsa:dev -n airbyte-abctl
after that you can configure connector in UI
i don’t know that new step
really appreciate it