Назар Тутин
12/03/2025, 1:00 PMkapa.ai
12/03/2025, 1:01 PMairbyte-db-0): bash kubectl get pods --all-namespaces | grep db - Run pg_dump inside the pod: bash kubectl exec -n <namespace> -it <database_pod> -- bash -c "pg_dump -U airbyte db-airbyte > /tmp/airbyte_backup.sql" - Copy backup locally: bash kubectl cp <namespace>/<database_pod>:/tmp/airbyte_backup.sql ./airbyte_backup.sql [[How to upgrade](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#how-to-upgrade)] 2. Add the V2 Helm repo bash helm repo add airbyte-v2 <https://airbytehq.github.io/charts> helm repo update helm search repo airbyte-v2 [[How to upgrade](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#how-to-upgrade)] 3. Decide namespace strategy - With external DB: recommended to install V2 into a new namespace (e.g. airbyte-v2), then point it to the same external DB and storage. [[How to upgrade](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#how-to-upgrade)] - With internal DB: you typically reuse the existing namespace and reinstall there so your PVC and DB pod are reused. [[How to upgrade](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#how-to-upgrade)] 4. Uninstall the old Helm release (do NOT delete namespace/PVCs) bash helm uninstall airbyte -n <namespace> Keep the namespace so the DB/storage remain. [[Deploy Airbyte](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#deploy-airbyte)] 5. Install Airbyte using Helm chart V2, targeting 1.8.5 First, find which V2 chart maps to app version 1.8.5 (for example, 2.0.17 in the docs): [[Deploy Airbyte](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#deploy-airbyte)] bash helm search repo airbyte-v2 --versions Then install into the chosen namespace with the matching chart version, e.g.: bash helm install airbyte airbyte-v2/airbyte \ --namespace <namespace> \ --values ./values.yaml \ --version 2.0.17 # chart that corresponds to app 1.8.5 (If you explicitly pin the image tag, use --set global.image.tag=1.8.5 as shown for 1.7.0 in the 1.8 docs.) [[1.8 Deploy Airbyte](https://docs.airbyte.com/platform/1.8/deploying-airbyte/chart-v2-community#deploy-airbyte)] 6. Restore DB only if something goes wrong The normal upgrade path reuses your DB (PVC or external DB). You only restore from the SQL backup if the upgrade breaks the deployment in a way not caused by misconfig. [[Deploy Airbyte](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#deploy-airbyte)] If needed, the restore flow is: bash # copy backup into DB pod kubectl cp ./airbyte_backup.sql airbyte/airbyte-db-0:/tmp/airbyte_backup.sql # drop & recreate schema (destructive!) kubectl exec -n airbyte -it airbyte-db-0 -- bash -c \ "psql -U airbyte -d db-airbyte -c 'DROP SCHEMA public CASCADE; CREATE SCHEMA public;'" # restore backup kubectl exec -n airbyte -it airbyte-db-0 -- bash -c \ "psql -U airbyte -d db-airbyte < /tmp/airbyte_backup.sql" [[Deploy Airbyte](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#deploy-airbyte)] --- About 1.4.0 → 1.8.5 specifically The docs state Helm chart V2 is supported for Airbyte 1.6.0+ when installed/managed with Helm. [[Upgrade to Helm chart V2](https://docs.airbyte.com/platform/1.8/enterprise-setup/chart-v2-enterprise)] The knowledge sources do not describe a documented, direct path from 1.4.0 to 1.8.5 with chart V2. They also don’t cover whether an intermediate upgrade (e.g., 1.4.0 → 1.6.x with chart V1, then to chart V2) is required or recommended. Because of that, I can’t confidently outline the exact intermediate steps for 1.4.0. Given you’re making a multi-version and chart-format jump, the docs recommend involving Airbyte support/Solution Architect for Enterprise or complex environments. [[Upgrade to Helm chart V2](https://docs.airbyte.com/platform/enterprise-setup/chart-v2-enterprise)] Summary - Data (connections, jobs, etc.) is preserved via the database, not via a separate import/export feature. - The supported V2 process is: backup DB → uninstall old release (keep namespace/storage) → install with chart V2 targeting the desired version → restore DB only if necessary. - For a 1.4.0 → 1.8.5 + V2 jump, the docs do not fully cover the exact upgrade path; consider doing an intermediate Helm V1 upgrade and/or contacting Airbyte for guidance.