@kapa.ai We want to upgrade our self-hosted Airbyte from version 1.5.1 to 2.0.1. At the same time, we will also move Airbyte to a new instance. What is the recommened approach to migrate the existing connection to the new upgraded instance of Airbyte. Is there a step-by-step guideance?

Here's the recommended approach for upgrading from Airbyte 1.5.1 to 2.0.1 while moving to a new instance, based on the available documentation. Recommended Approach: Fresh Install with External Database The cleanest path when moving to a new instance is to use an external database and deploy Airbyte fresh using Helm chart V2. Here are the steps: Step 1: Backup Your Existing Database Before anything else, back up Airbyte's internal Postgres database from your current instance: 1. Find your database pod:kubectl get pods --all-namespaces | grep db 2. Run

pg_dump

inside the Postgres pod:kubectl exec -n namespace -it database_pod -- bash -c "pg_dump -U airbyte db-airbyte > /tmp/airbyte_backup.sql" 3. Copy the backup locally:kubectl cp airbyte/airbyte-db-0:/tmp/airbyte_backup.sql ./airbyte_backup.sql [Helm chart V2 upgrade] Step 2: Add the Helm Chart V2 Repository Helm chart V2 uses a different repo URL than V1:

helm repo add airbyte-v2 https://airbytehq.github.io/charts
helm repo update

[Helm chart V2 upgrade] Step 3: Prepare a New Namespace Create a new namespace for the upgraded Airbyte instance (recommended when using an external database):

kubectl create namespace airbyte-v2

[Helm chart V2 upgrade] Step 4: Identify the Correct Helm Chart Version Find the chart version corresponding to Airbyte 2.0.1:

helm search repo airbyte-v2 --versions

Based on the documentation,

chart version 2.0.1

corresponds to

app version 1.6.1

. For Airbyte 2.0.0, use chart version

2.0.18

. [Deploy Airbyte] Step 5: Create a New values.yaml and Deploy Prepare your new

values.yaml

file and install Airbyte into the new namespace:

helm install airbyte airbyte-v2/airbyte \
  --namespace airbyte-v2 \
  --values ./values.yaml \
  --version 2.0.18

[Deploy Airbyte] Important Notes • Breaking changes: Since you're jumping from 1.5.1 to 2.0.x, review the breaking changes documented at https://docs.airbyte.com/release_notes/breaking-changes to understand what may need adjustment. [GitHub discussion] • Database copy across versions: A straight database dump/restore between significantly different versions is generally unreliable due to schema differences. [GitHub discussion] • If using an external database: You can point the new instance directly at the existing external database, which is the smoothest migration path. • If not using an external database: Restore the backup SQL into the new instance's Postgres pod before starting Airbyte. The knowledge sources do not provide a fully detailed step-by-step guide specifically for the 1.5.1 → 2.0.1 path with a database restore on a new instance, so I'd recommend also reviewing the official breaking changes page before proceeding. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.