I have an airbyte at 2.0.1 version and the ingress...
# replication-ask-ai
r
I have an airbyte at 2.0.1 version and the ingress-nginx at 1.15.1...I want to downgrade airbyte version for 1.8.5 without lose my data connections, is it possible?
k
Downgrading Airbyte from 2.0.1 to 1.8.5 is very likely not possible without data loss or connection issues. Here's why: The knowledge sources explicitly mention that starting from Airbyte version 1.8.0, Flyway database migrations are applied that update the internal schema. Once these migrations run, older binaries (i.e., a downgraded version) can no longer use the updated schema. As one user noted in a GitHub issue: > "It is not possible to simply downgrade Airbyte to an older version. On my case it was required to deploy a new instance and migrate the connections manually." [Refresh UI error issue] This means that after running 2.0.1, the internal Postgres database schema has been migrated forward, and rolling back to 1.8.5 would likely break the application since 1.8.5 binaries cannot interpret the newer schema. What you can do instead 1. Stay on 2.0.x: If there's a specific issue driving the downgrade, consider checking if a newer patch of 2.0.x resolves it. 2. Restore from a database backup: If you have a backup of Airbyte's internal Postgres database taken before the upgrade to 2.0.1, you could restore it and redeploy 1.8.5. The knowledge sources describe a database restoration process for Helm-based deployments [chart-v2-community], but this would only work if you have a pre-upgrade backup. 3. Deploy a fresh 1.8.5 instance and migrate manually: As mentioned in the community, you can deploy a new Airbyte instance at 1.8.5 and recreate your sources, destinations, and connections manually. In summary, a seamless in-place downgrade from 2.0.1 to 1.8.5 while preserving all data connections is not supported due to irreversible database schema migrations. The knowledge sources do not describe any official downgrade path for this scenario. šŸ‘ 0 button šŸ‘Ž 0 button ā„¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
r
@kapa.ai it was at 1.5 version before
k
Based on the conversation history, it sounds like you're clarifying that your Airbyte was previously at version 1.5.x before you upgraded to 2.0.1, and you want to go back to 1.8.5. Unfortunately, this doesn't change the situation — it actually makes it more complex. Since you've already upgraded from 1.5.x all the way to 2.0.1, the database schema has gone through multiple forward migrations across many versions. Rolling back to 1.8.5 would still face the same fundamental problem: the schema applied by 2.0.x is incompatible with 1.8.5 binaries. The knowledge sources do not describe any supported downgrade path between these versions. What they do suggest for similar situations is: • A fresh install of the target version, then manually recreating your connections, sources, and destinations — or using the Airbyte API/Terraform to export and reimport configurations. [abctl migrate discussion] • Restoring from a pre-upgrade database backup, but only if you have a backup taken before the upgrade to 2.0.1 (and ideally at the version you want to return to). [chart-v2-community] If you don't have such a backup, a clean reinstall of 1.8.5 with manual reconfiguration is the only realistic path the knowledge sources support. šŸ‘ 0 button šŸ‘Ž 0 button ā„¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.