@kapa.ai Deploying v2 helm chart and receive this error mapping key "DATAPLANE_CLIENT_ID_SECRET_KEY" already defined at line 24 line 220: mapping key "DATAPLANE_CLIENT_SECRET_SECRET_KEY" already defined at line 25

This is a known issue in the v2 Helm chart: the generated

airbyte-airbyte-env

ConfigMap contains duplicate keys for: -

DATAPLANE_CLIENT_ID_SECRET_KEY

-

DATAPLANE_CLIENT_SECRET_SECRET_KEY

because both

airbyte.auth.bootstrap.configVars

and

airbyte.workloadLauncher.dataPlane.configVars

are included unconditionally in

env-configmap.yaml

and each defines those keys. [[Duplicate keys issue](https://github.com/airbytehq/airbyte/issues/66546)] This causes validation errors like:

text key "DATAPLANE_CLIENT_ID_SECRET_KEY" already set in map key "DATAPLANE_CLIENT_SECRET_SECRET_KEY" already set in map

The issue has been reproduced by the Airbyte team and they’ve stated they’re working on a fix to be released in an upcoming chart version, but the knowledge sources do not yet document a released version where it is fixed. [[Duplicate keys reproduced](https://github.com/airbytehq/airbyte/issues/66546)] Because the provided sources don’t contain an official workaround, I can’t give you a supported patch beyond confirming: - Your error is caused by this duplicate‑key bug in the v2 chart. - It affects at least versions 2.0.0–2.0.18. [[Duplicate keys versions](https://github.com/airbytehq/airbyte/issues/66546)] If you need to proceed before an updated chart is available, the only options implied by the GitHub discussion are to: - Relax/disable strict YAML validation in your tooling for this chart, or - Locally modify the chart templates (e.g., add the suggested conditional around one of the includes) — but this is not described or endorsed as an official fix in the current docs. [[Suggested condition](https://github.com/airbytehq/airbyte/issues/66546)] For an official resolution, you’ll need to upgrade to the first v2 chart version where this issue is fixed once it’s published.