@kapa.ai: Workload launcher fails with Caused by: java.io.IOException: HTTP error: 500 Internal Server Error

This error typically occurs when the connector-sidecar fails to write its output to the Workload API Server, resulting in a

DocStoreAccessException

. Here's what's known about this issue: Root Cause The connector itself may complete successfully, but the connector-sidecar fails when trying to report results back to the Workload API Server:

DocStoreAccessException: Unable to write output for <workload-id>_check

This is caused by the connector-sidecar not having the necessary authentication credentials to communicate with the Workload API Server. [Connector-Sidecar Auth Issue] Affected Deployments This issue has been reported on Airbyte OSS v2.0.1 deployed on Kubernetes/Helm. [HTTP 500 Issue] Potential Workaround (Kubernetes/Helm) The issue is related to the Workload API authentication configuration. Ensure the following environment variables are properly set and propagated to the connector-sidecar containers: •

API_AUTHORIZATION_ENABLED=true

•

WORKLOAD_API_AUTH_HEADER

(e.g.,

Authorization

) •

WORKLOAD_API_BEARER_TOKEN

(your generated token) You can configure these in your Helm values under `workloadApiServer.extraEnv`:

workloadApiServer:
  extraEnv:
    - name: WORKLOAD_API_AUTH_HEADER
      value: "Authorization"
    - name: WORKLOAD_API_BEARER_TOKEN
      value: "[your-generated-token]"

[Connector-Sidecar Auth Issue] > ⚠️ Known Limitation: There is a known issue where these tokens may not properly propagate to connector-sidecar containers. This is still an open issue being tracked by the Airbyte team. [HTTP 500 Issue] If you are still experiencing the issue after trying the above, it is recommended to provide your Airbyte version, deployment method, and Helm chart version when reporting to the Airbyte team for further investigation. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.