@kapa.ai Where can I found information about these keys for custom values and secrets yaml files ? CONFIG_DATABASE_REPLICA_USER

I'm sorry, but there's no information about

CONFIG_DATABASE_REPLICA_USER

in the knowledge sources provided. This key does not appear in any of the Airbyte documentation covering configuration variables,

values.yaml

references, or Kubernetes secrets setup. The knowledge sources do document related database configuration keys such as: •

CONFIG_DATABASE_USER

– Defines the Configs Database user (defaults to the Jobs Database user if empty) [Configuring Airbyte] •

DATABASE_USER

– Defines the Jobs Database user [Configuring Airbyte] However,

CONFIG_DATABASE_REPLICA_USER

is not mentioned anywhere in the available documentation. For the most up-to-date and complete list of supported configuration keys, I'd recommend checking: • The Values.yaml reference directly on the Airbyte docs site [Values.yaml reference] • The full values.yaml on GitHub • The Airbyte community forum or GitHub issues for any undocumented/alpha configuration options 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai I don't understand why is failing: WARNING Encountered an issue deploying Airbyte: Pod: airbyte-abctl-bootloader.18bfac5da1d8c676 Reason: Failed Message: Error: couldn't find key CONFIG_DATABASE_REPLICA_USER in Secret airbyte-abctl/airbyte-config-secrets Count: 10 This is a official error from local helm deployment with version 2.1.0

I'm sorry, but the knowledge sources do not contain specific information about

CONFIG_DATABASE_REPLICA_USER

or why it would be required in Helm chart v2.1.0. However, based on a similar documented issue, this error pattern is familiar. In Helm chart v2, the chart expects certain keys to exist in the

airbyte-config-secrets

Kubernetes secret before deployment. If a key referenced by the chart is missing, all pods referencing that environment variable will fail to start. [GitHub Issue] A likely workaround (similar to the

AIRBYTE_DUMMY_SECRET

issue) would be to patch your secret with a placeholder value:

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

Or recreate it including the key:

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

That said, I'd strongly recommend: 1. Filing a GitHub issue with the Airbyte team, as this appears to be an undocumented requirement introduced in v2.1.0 — similar to the previously reported

AIRBYTE_DUMMY_SECRET

problem. [GitHub Issue] 2. Checking the Values.yaml reference and the Preconfiguring Kubernetes Secrets docs for any updated requirements in v2.1.0. [Secrets docs] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai How can I deploy my airbyte instance with a specific helm chart version ? I'm trying something like this abctl local install --values airbyte_values_prod.yaml --secret airbyte_secrets_prod.yml --version 2.0.0

The flag you're using is wrong. For

abctl

, the correct flag to specify a Helm chart version is

--chart-version

, not

--version

. Here is the corrected command:

abctl local install --chart-version 2.0.0 --values airbyte_values_prod.yaml --secret airbyte_secrets_prod.yml

A few important notes: • The

--chart-version

value refers to the Helm chart version, not the Airbyte platform version. These don't necessarily share the same version number. [abctl reference] • You can find all available Helm chart versions and their corresponding Airbyte platform versions on ArtifactHub. [abctl reference] •

--secret

can be set multiple times if you have more than one secrets file. [abctl reference] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai Se puede fijar una versión de Helm chart en airbyte_values_prod.yaml ?

No, la versión del Helm chart no se puede fijar dentro del archivo

values.yaml

. El archivo

values.yaml

solo sirve para personalizar la configuración de la instalación (base de datos, secretos, recursos, etc.), no para controlar qué versión del chart se despliega. La versión del Helm chart debe especificarse siempre mediante el flag

--chart-version

directamente en el comando de instalación: [abctl reference]

abctl local install --chart-version 2.0.18 --values airbyte_values_prod.yaml --secret airbyte_secrets_prod.yml

Si necesitas reproducir un despliegue conocido o mantenerte en una versión específica, la recomendación es incluir siempre el flag

--chart-version

explícitamente en tu comando de instalación. [abctl install] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.