@kapa.ai The Airbyte helm chart (2.0.19) uses two

DATAPLANE_CLIENT_ID_SECRET_KEY

keys in the env-configmap. This is causing our code checks to fail. Is it possible to configure things such that only one

DATAPLANE_CLIENT_ID_SECRET_KEY

key is put into the env-configmap?

You’ve run into a known issue with the v2 Helm chart: duplicate

DATAPLANE_CLIENT_ID_SECRET_KEY

(and

DATAPLANE_CLIENT_SECRET_SECRET_KEY

) entries are rendered into the

airbyte-airbyte-env

ConfigMap because two templates both emit the same keys and are included unconditionally. [[Duplicate keys issue](https://github.com/airbytehq/airbyte/issues/66546)] From the knowledge sources: -

airbyte.auth.bootstrap.configVars

generates

DATAPLANE_CLIENT_ID_SECRET_KEY

/

DATAPLANE_CLIENT_SECRET_SECRET_KEY

. -

airbyte.workloadLauncher.dataPlane.configVars

also generates those same keys. -

env-configmap.yaml

includes both templates without conditions, which produces duplicate keys. [[Duplicate keys issue](https://github.com/airbytehq/airbyte/issues/66546)] The docs/issues do not describe any chart values or configuration flags that let you disable one of these includes or otherwise avoid the duplicate key purely via

values.yaml

. The suggested fix in the issue is a chart change (adding conditionals in the templates), not a runtime configuration option. [[Duplicate keys issue](https://github.com/airbytehq/airbyte/issues/66546)] The only workaround mentioned in the sources is to override the named template from a parent chart so it doesn’t emit the duplicate keys: > “if you have a parent chart with airbyte as dependencies, it’s still possible to override the named template in the parent chart so it does not generate the duplicate keys…” [[Duplicate keys issue](https://github.com/airbytehq/airbyte/issues/66546)] So, based on the available information: - There is no documented way in chart 2.0.x to configure values so that only one

DATAPLANE_CLIENT_ID_SECRET_KEY

is rendered into the env ConfigMap. - The practical options (per the sources) are: - Override the relevant named template(s) in a parent chart to remove one set of keys, or - Wait for / upgrade to a chart version where the upstream templates have been fixed. If you need, I can outline how a parent chart override would look conceptually, but the exact template code is not provided in the knowledge sources.