@kapa.ai Upgrading to 2.1.0 version and bootloader shows warning Error: couldn't find key CONFIG_DATABASE_REPLICA_USER in Secret airbyte-v3/airbyte-config-secrets any workarounds?

The knowledge sources don't explicitly mention

CONFIG_DATABASE_REPLICA_USER

as a key, but this error is very similar to a known pattern with Airbyte's Helm chart v2 where pods fail because an expected key is missing from the

airbyte-config-secrets

Kubernetes secret. Based on a closely related issue documented in the knowledge sources, the workaround is to add the missing key to your

airbyte-config-secrets

secret. You can patch the existing secret to add the missing key:

kubectl patch secret airbyte-config-secrets -n airbyte-v3 \
  --type merge \
  -p '{"stringData": {"CONFIG_DATABASE_REPLICA_USER": "dummy"}}'

Or if you prefer to recreate/update it with `kubectl`:

kubectl create secret generic airbyte-config-secrets \
  --from-literal=CONFIG_DATABASE_REPLICA_USER='your-value' \
  --namespace airbyte-v3 \
  --dry-run=client -o yaml | kubectl apply -f -

A similar issue was documented for

AIRBYTE_DUMMY_SECRET

, where the Helm chart expected a key to exist in the

airbyte-config-secrets

secret but it wasn't present, causing all pods to fail to start. [Github Issue] Important caveats: • If

CONFIG_DATABASE_REPLICA_USER

is meant to be a real replica database user (not a dummy placeholder), you should set it to the actual value rather than a placeholder. • The knowledge sources do not contain specific documentation about this key for version 2.1.0, so I cannot confirm whether this is a bug in the chart or an intentional new requirement. You may want to check the Airbyte GitHub issues or reach out to the Airbyte community for more specific guidance on this key in v2.1.0. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.