Summary
When setting up a new Airbyte instance on K8s with Helm Chart, is there a way to migrate existing connections from the old Docker Compose instance by copying over folders or files?
Question
Hi all. I currently have an Airbyte instance running on Docker Compose. If I were to set up a completely new instance using K8s with helm chart, is there a way to migrate all my existing connections from my old instance? Maybe I can just copy over some folders or files?
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.
Join the conversation on Slack
["migrating-connections", "airbyte-instance", "docker-compose", "k8s", "helm-chart"]
Configuration is stored in PostgreSQL database (db or similar name of container)
I’d recommend configuring external database.
https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#external-airbyte-database
It increases cost of infrastructure, but it gives a way more flexibility. When Airbyte connects to database, it detects database’s state, and perform database migrations if necessary.
You could dump all the data from one database and import it to another.
Hi, i have same problem, how to you point the new airbyte instance to the database ?
Read docs, there is a link above. Shortly, for helm charts, you need to use values.yaml with proper configuration.
Okay thanks, but how did you find this page ? https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#external-airbyte-database I searched for 1 week webpage like this one but never found
I guess I was visiting this page quite often. I can see there were some re-arrangements recently.
From https://docs.airbyte.com/deploying-airbyte/ you can find link to https://docs.airbyte.com/deploying-airbyte/integrations/database