Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT> After i do an upgrade to airbyte to v2.1, whats the correct procedure to follow with secrets in keyvaults. Do i need to re-enter the passwords to all connectors, thats a bad upgrade experienece

Good news — you generally do *not* need to re-enter passwords for all connectors after upgrading to Airbyte v2.1, *as long as your secret manager configuration remains unchanged*.

However, there is one important caveat directly from the docs:

> *Modifying the configuration of connector secret storage will cause all existing connectors to fail.* You will need to recreate these connectors to ensure they are reading from the appropriate secret store. [<https://docs.airbyte.com/platform/deploying-airbyte/integrations/secrets#values|Secret Management>]
So the key question is: *are you changing your secrets manager configuration during the upgrade?*

 If you are NOT changing your secrets manager config If your `values.yaml` keeps the same `global.secretsManager` settings (same type, same secret name, same credentials), your connectors should continue reading from the key vault without any re-entry of credentials.

 If you ARE changing your secrets manager config (or migrating to one) For example, if you're moving from storing secrets in the internal database to Azure Key Vault, or changing the vault URL/credentials, then yes — existing connectors will break and you'll need to recreate them.

 Key things to check in your values.yaml when upgrading to v2.1 / Helm chart V2 Make sure your Azure Key Vault config uses the correct V2 keys. Here's the expected structure: [<https://docs.airbyte.com/platform/deploying-airbyte/integrations/secrets#values|Secret Management>]

```global:
  secretsManager:
    type: AZURE_KEY_VAULT
    secretName: "airbyte-config-secrets"
    azureKeyVault:
      vaultUrl: ## https://my-vault.vault.azure.net/
      tenantId: ## your-tenant-id
      clientId: ""
      clientIdSecretKey: ""
      clientSecret: ""
      clientSecretSecretKey: ""```
Also note that Helm chart V1 is *no longer supported* in v2.1, so if you haven't already migrated to Helm chart V2, you must do that first. [<https://docs.airbyte.com/release_notes/self-managed/v-2.1|Airbyte 2.1>] During that migration, some key names changed — for example, `global.database.database` became `global.database.name` — so double-check your full `values.yaml` for any renamed keys. [<https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community#update-your-valuesyaml-file|Upgrade to Helm chart V2>]

*Summary:* As long as you preserve your existing secrets manager configuration without changes, you should not need to re-enter connector credentials. :thumbsup: 0 button :thumbsdown: 0 button :information_source: *Tip:* Mention *@kapa.ai* in the thread for follow-ups or *DM the app* for *1-to-1* help.