Summary
User wants to migrate Airbyte from Docker Compose to GKE, facing issues creating a Helm chart for version 0.50.33.
Question
Hello everyone,
I want to migrate Airbyte (v0.50.33) running on Docker Compose to GKE. I plan to first deploy v0.50.33 on GKE, perform the DB migration, and then upgrade to the latest version. However, I am unable to create a Helm chart for version 0.50.33.
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
["migrate", "airbyte", "docker-compose", "gke", "helm-chart", "version-0.50.33"]
Keep in mind that the historical helm chart versions don’t directly align to the application versions. You can see this by doing a:
helm search repo 'airbyte/airbyte' --versions
In this case, it looks like the latest chart version matching application version 0.50.33 is chart version 0.49.20
So you’ll pass this to helm install using the --version flag (you may need to quote it, depending on the platform/helm version)
If you really want to be pedantic (like I clearly do), the above over-matches all the Airbyte charts since they start with airbyte/airbyte. So you can also use the shorthand for --versions (-l) and use -r to search it as a regular expression. A particular oddity of helm is that you can’t match on the end of the string with $ like you normally would, but rather need to match a vertical tab in the list output with \v. Putting it all together:
helm search repo -l -r "airbyte/airbyte\v"
. . . will search only for the primary chart, not the individual components.
(Trust me, you’ll be the life of the party with this bit of trivia)