<@U04S8PLJWMT> Error: couldn't find key WORKLOAD_A...
# ask-ai
e
@kapa.ai Error: couldn't find key WORKLOAD_API_BEARER_TOKEN in Secret airbyte/airbyte-airbyte-secrets. this is happening on airbyte 2.0.1 v1 helm chart
k
This error means your deployment expects a
WORKLOAD_API_BEARER_TOKEN
key in the
airbyte-airbyte-secrets
Secret, but that key is missing. This is consistent with other issues where the token is required but not automatically populated in some Helm setups. [[workload pods](https://github.com/airbytehq/airbyte/issues/50979); [stuck installing](https://github.com/airbytehq/airbyte/issues/52091)] Since you’re on Airbyte 2.0.1 with the V1 Helm chart, there are two important points: 1. V1 chart + 2.0.x is problematic The maintainers have confirmed that V1 Helm charts for 2.0.0 / 2.0.1 were removed and are not meant to be used; the recommended paths are: - Stay on Airbyte 1.8.5 with V1 chart, or - Move to V2 Helm chart from the
airbyte-v2
repo to run Airbyte 2.x. [[helm error 2.0.1](https://github.com/airbytehq/airbyte/issues/68136)] 2. Workaround: manually add
WORKLOAD_API_BEARER_TOKEN
to the Secret
Until you migrate, you can unblock the deployment by adding a token key to
airbyte-airbyte-secrets
so pods that reference it don’t fail. The exact, supported command sequence is not documented for this Secret in the sources, but a closely related pattern is shown for the abctl local install secrets and for fixing 502/issues with the workload bearer token. [[502 bearer token](https://github.com/airbytehq/airbyte/issues/65567); [abctl workload token](https://github.com/airbytehq/airbyte/issues/65574)] Because the knowledge sources do not provide an explicit, step‑by‑step fix for this exact key/Secret combination on Helm V1 + 2.0.1, I can’t safely give you concrete
kubectl
commands tailored to that Secret without guessing. Recommended resolution: - Preferred: - If you want Airbyte 2.x, follow the documented upgrade path to Helm chart V2 (
airbyte-v2
repo) and install a supported 2.x version from there. [[upgrade to v2 chart](https://docs.airbyte.com/platform/1.8/deploying-airbyte/chart-v2-community#how-to-upgrade); [helm error 2.0.1](https://github.com/airbytehq/airbyte/issues/68136)] - If you want to stay on V1 Helm charts, run Airbyte 1.8.5 (which is reported to work well). [[helm error 2.0.1](https://github.com/airbytehq/airbyte/issues/68136)] - Temporary workaround (if you must keep this combo): - Manually ensure
WORKLOAD_API_BEARER_TOKEN
exists in whatever Secret your pods reference (here,
airbyte-airbyte-secrets
), similar in spirit to how users generate and inject a bearer token for abctl/local workloads. [[workload pods](https://github.com/airbytehq/airbyte/issues/50979); [abctl workload token](https://github.com/airbytehq/airbyte/issues/65574)] - The exact commands are not documented in these sources, so proceed with caution and consider aligning with the V2 chart behavior instead. If you can share your
values.yaml
and which repo/chart version you installed from, you may be able to cross‑check whether you’re unintentionally using a chart combination that the maintainers have already deprecated.
e
I'm on airbyte 2.0.1, with 1.9.1 v1 helm chart @kapa.ai
k
A message from kapa.ai
You’ve hit a combination that is known to be confusing but is intentionally supported: - Airbyte 2.0.1 + Helm V1 chart 1.9.1 is the correct pairing if you want to stay on the V1 chart. After the bad 2.0.0 / 2.0.1 charts were removed, the maintainers explicitly stated that chart 1.9.1 installs Airbyte 2.0.1. [[helm 1.9.1→2.0.1](https://github.com/airbytehq/airbyte/issues/68136)]
Copy code
text   helm install airbyte airbyte/airbyte --namespace airbyte --version 1.9.1   # installs Airbyte 2.0.1
- The earlier “2.0.0” and “2.0.1” V1 charts in the
airbyte/airbyte
repo were removed and should not be used. [[2.0.0 charts removed](https://github.com/airbytehq/airbyte/issues/68136)] That said, maintainers also acknowledge some “weirdness” with using V1 chart on 2.0.x and suggest that if you run into issues, you may want to: - Either stay on 1.8.5 (V1 chart) which is reported as stable, or - Migrate to Helm chart V2 (from the
airbyte-v2
repo) and run Airbyte 2.x there; this path is working well and will become the standard. [[multiple issues v2](https://github.com/airbytehq/airbyte/issues/68134); [helm error 2.0.1](https://github.com/airbytehq/airbyte/issues/68136); [upgrade to v2 chart](https://docs.airbyte.com/platform/deploying-airbyte/chart-v2-community)] So: - Your versions match what maintainers intend (Airbyte 2.0.1 + chart 1.9.1). - If you keep seeing the
WORKLOAD_API_BEARER_TOKEN
Secret error on this combo, it’s not covered in detail in the docs/issues provided; the sources don’t give an official fix for that specific Secret/key on V1 chart 1.9.1 + 2.0.1, only related patterns and general advice. - The documented, supported escape hatch is to migrate to Helm chart V2 (
airbyte-v2
repo) for Airbyte 2.x, or to run 1.8.5 on V1 chart.
e
@kapa.ai I want to fix that on the current airbyte deployment, no migration to v2
k
A message from kapa.ai
You can work around this on your current 2.0.1 + Helm v1.9.1 deployment by creating/patching the Secret so the
WORKLOAD_API_BEARER_TOKEN
key exists
, reusing the patterns shown for workload bearer tokens in the GitHub issues. From the manifests in the “workload pods are missing the service account” issue, we know the deployment is expecting:
Copy code
yaml - name: WORKLOAD_API_BEARER_TOKEN   valueFrom:     secretKeyRef:       key: WORKLOAD_API_BEARER_TOKEN       name: airbyte-airbyte-secrets
[[workload pods](https://github.com/airbytehq/airbyte/issues/50979)] So the fix is to ensure that key exists in the
airbyte-airbyte-secrets
Secret. The docs show how to create/patch a generic Secret for Airbyte using
kubectl
(example is for
airbyte-config-secrets
, but the same mechanism applies to
airbyte-airbyte-secrets
). [[creating secrets](https://docs.airbyte.com/platform/deploying-airbyte/creating-secrets)] ### 1. Generate a token Inside a shell that has access to your cluster:
Copy code
bash WORKLOAD_TOKEN=$(openssl rand -hex 32) echo "Generated token: $WORKLOAD_TOKEN"
(The same pattern is used in the 502/bearer-token issues for abctl/local installs. [[502 bearer](https://github.com/airbytehq/airbyte/issues/65567); [abctl workload token](https://github.com/airbytehq/airbyte/issues/65574)]) ### 2. Add
WORKLOAD_API_BEARER_TOKEN
to
airbyte-airbyte-secrets
If the Secret already exists, patch it:
Copy code
bash kubectl patch secret airbyte-airbyte-secrets \   -n airbyte \   --type merge \   -p "{\"stringData\": {\"WORKLOAD_API_BEARER_TOKEN\": \"${WORKLOAD_TOKEN}\"}}"
If for some reason the Secret does not exist, create it (be careful not to blow away existing data—this command is only safe if the Secret truly doesn’t exist):
Copy code
bash kubectl create secret generic airbyte-airbyte-secrets \   --from-literal=WORKLOAD_API_BEARER_TOKEN="${WORKLOAD_TOKEN}" \   -n airbyte
(The create/patch style is directly aligned with the documented pattern for `airbyte-config-secrets`; only the name/key differ. [[creating secrets](https://docs.airbyte.com/platform/deploying-airbyte/creating-secrets)]) ### 3. Restart affected deployments Now restart the workloads that reference this Secret so they re-read the environment value. The exact deployments are not listed in the docs for the Helm chart, but you will likely need at least the worker components (similar to the abctl fixes that require restarting
airbyte-abctl-worker
and
airbyte-abctl-workload-api-server
). [[502 bearer](https://github.com/airbytehq/airbyte/issues/65567); [local 502 fix](https://github.com/airbytehq/airbyte/issues/66692)] For example:
Copy code
bash kubectl rollout restart deployment airbyte-worker -n airbyte kubectl rollout restart deployment airbyte-server -n airbyte
You may need to adjust deployment names to match your cluster (
kubectl get deploy -n airbyte
). --- Limitations: the knowledge sources do not contain an official, version‑specific guide for this exact
WORKLOAD_API_BEARER_TOKEN
error on Helm v1.9.1 + Airbyte 2.0.1; the commands above are derived by combining: - The documented way to create/patch Secrets for Airbyte. [[creating secrets](https://docs.airbyte.com/platform/deploying-airbyte/creating-secrets)] - The manifest snippet showing
WORKLOAD_API_BEARER_TOKEN
is expected in
airbyte-airbyte-secrets
. [[workload pods](https://github.com/airbytehq/airbyte/issues/50979)] - The established pattern for generating and wiring a bearer token in similar 502/auth issues. [[502 bearer](https://github.com/airbytehq/airbyte/issues/65567); [abctl workload token](https://github.com/airbytehq/airbyte/issues/65574)] So this is a reasonable, documented-style workaround, but not an officially published “fix” specific to this exact Helm + version combo.