<@U04S8PLJWMT> I'm seeing this log message in Kube...
# replication-ask-ai
s
@kapa.ai I'm seeing this log message in Kuberneter:
container airbyte-workload-api-server-container is not valid for pod rce-mssql-discover-e87bdb9f-ad13-4e2f-a367-c1654ee5171a-0-zswre
when trying to update a connection via API
k
I'm sorry, but the provided knowledge sources do not contain information regarding the specific error message:
container airbyte-workload-api-server-container is not valid for pod
. While the sources discuss various issues with the Workload API Server and pods during connector operations (like
DISCOVER
), they do not explicitly mention this "not valid for pod" error. However, based on the documentation of Airbyte's architecture, here are some relevant points regarding how these components interact: * Workload Architecture: In Airbyte's current architecture, the Workload API Server receives requests to create workloads (such as a
DISCOVER
job for MSSQL). The Launcher then picks up these jobs and launches the actual Kubernetes pods [[Understanding Airbyte Jobs](https://docs.airbyte.com/platform/understanding-airbyte/jobs)]. * Authentication Mismatches: Several users have reported 502 or 401 errors when the
WORKLOAD_API_BEARER_TOKEN
is not synchronized between the Worker and the Workload API Server. A suggested fix is to manually align these tokens across deployments [[Github Issue 65567](https://github.com/airbytehq/airbyte/issues/65567); [Github Issue 66692](https://github.com/airbytehq/airbyte/issues/66692)]. * Deployment Inconsistencies: There are reports of the
airbyte-workload-api-server
failing to update correctly during Helm chart upgrades, which can cause version mismatches or invalid deployment specs [[Github Issue 53180](https://github.com/airbytehq/airbyte/issues/53180); [Github Issue 65129](https://github.com/airbytehq/airbyte/issues/65129)]. If you are seeing this error when using the API, it may indicate a configuration or version mismatch in how the Workload API Server is attempting to provision the pod. You might consider restarting the
airbyte-abctl-worker
and
airbyte-abctl-workload-api-server
deployments to ensure they are in a clean state [[Github Issue 66692](https://github.com/airbytehq/airbyte/issues/66692)].