Summary
Upgrading Airbyte version in a K8s deployment without losing source and destination configurations
Question
Hi there!
We use Airbyte deployed with K8s and a <https://airbytehq.github.io/helm-charts/|helm chart> to load some data into BigQuery. Do any of you know how to upgrade the Airbyte version without deleting all the source and destination configurations ? Asking for a friend … 
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
["upgrade", "airbyte-version", "k8s", "helm-chart", "bigquery", "source-configuration", "destination-configuration"]
Hi Luc, I don’t know about other people’s experiences, but when we upgraded our helm chart, it never affected our sources/destination configurations… I don’t know if it’s just because we use external storage and database, but I didn’t think so…? (unless you delete the namespace in the process or so)
<@U07BR7EUU0P> This should never happen. Did you delete the volume/persistent-volumes when you executed the upgrade? My recommendation is to enable the external database. This will reduce the risk of problems like this.
I’ll give it a shot, thank you 
There is documentation for how to integrate an external database here: https://docs.airbyte.com/deploying-airbyte/integrations/database