Frustrating eye-opening Airbyte Upgrade Experience...
# connector-contributions
b
Frustrating eye-opening Airbyte Upgrade Experience I’m quite suprised by what we’ve just gone through trying to update our Airbyte instance on GCP Compute Engine. We were stuck on version 0.50.35, so an upgrade was long overdue. But what we found was pretty eye-opening: 1. Silent in the night, docker compose support dropped: Without much fanfare, Airbyte quietly announced in this June 2024 release note that Docker Compose is no longer supported. If you can’t find the update, it’s the very last paragraph. Kubernetes is now the only recommended deployment method. Why? Because Docker Compose is apparently too tricky to upgrade. But what about the users still on it? 2. Docs taken down: The official guide for upgrading via Docker Compose? Gone. They’ve completely wiped it from their current documentation. We had to rely on a webarchive version just to get through the process. How are users supposed to upgrade if the method they rely on just disappears? 3. uhhh, migration guides? That’s probably something that should be available yes? This feels a bit suspicious—is Airbyte making these processes harder than necessary to push users (or even discourage) from self-hosting to their paid services while still benefiting from open-source contributions to expand their platform? 🤔
👍 1
c
We encountered the same issue, and even had breaking change when they dropped the normalisation process..
💔 2
😢 1
b
Did you solve it? @cyprien barbault (fyi this was what we found and it worked) And what normalisation process? 👀
c
Well we're going to have to migrate the abctl as there is no other way now
u
1. The team sent announcements messages in #announcements and #releases, an special mention in the Airbyte newletter and a Github Discussion. If you have a suggestion to improve the way to communicate breaking changes we’re more than happy to hear 👂 octavia thanks . a. Docker-Compose was deprecated but you can use
abctl
which only requirement is Docker. b. Here is the migration guide from users on Docker Compose. 2. Yes, deprecating a feature is complicated and sometimes involves making tough decisions. If we keep deprecated documentation, people will continue to use Docker Compose, even though it is broken and not maintained, instead of migrating to the new method. 3. Maybe we can find add migration guide in other part of documentation. You can help doing suggestions too octavia loves !
2. From your comment maybe we can include some note until everyone migrated in the Upgrading Airbyte
cc @Natalie (Airbyte)
1. Maybe next time we can also add header warning in the documentation like install/upgrade.