@kapa.ai I am installing Airbyte via helm chart 2.0.19 and using an external database. The bootloader pod has a CreateContainerConfigError status : couldn't find key DATABASE_USER in Secret airbyte/airbyte-external-db-creds. Any thoughts?

The error suggests Kubernetes is looking for a key named

DATABASE_USER

in your secret, but for Helm chart–based external DB configuration Airbyte expects the keys

database-user

and

database-password

instead. [External DB] For Helm chart V2, the documented pattern is: 1. Create the secret with these keys (in the same namespace as Airbyte):

apiVersion: v1
   kind: Secret
   metadata:
     name: airbyte-external-db-creds   # or airbyte-config-secrets
     namespace: airbyte
   type: Opaque
   stringData:
     database-user: your_db_user
     database-password: your_db_password

2. Reference that secret and keys in `values.yaml`:

postgresql:
     enabled: false

   global:
     database:
       type: external
       secretName: "airbyte-external-db-creds"

       host: "your-db-host"
       port: "5432"
       name: "your_db_name"

       userSecretKey: "database-user"
       passwordSecretKey: "database-password"

[External DB] If your current secret uses

DATABASE_USER

/

DATABASE_PASSWORD

as keys, either: • Rename them to

database-user

/

database-password

, or • Keep your keys and set

userSecretKey

/

passwordSecretKey

in

values.yaml

to match them. Also ensure the secret name and namespace in

values.yaml

exactly match the actual Secret. If after aligning the keys and secret name you still see

DATABASE_USER

referenced, that mapping is likely coming from your chart’s env config; in that case, adjust the secret keys or `userSecretKey`/`passwordSecretKey` so that the chart can populate `DATABASE_USER`/`DATABASE_PASSWORD` from `database-user`/`database-password`. [Configuring Airbyte; External DB] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.