Issue with Airbyte job orchestrator failing to connect to GCS

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

Job orchestrator in Airbyte on K8s fails to connect to GCS due to unauthenticated user error. Difficulty passing service account to orchestrator.


Question

Hii, I am finishing to deploy Airbyte on K8s using helm and connecting to GCS for logs and such. Im getting this issue in which the job orchestrator fails when trying to connect to storage because it doesn’t have a service account(Got a 401 with unauthenticated user). In my values.yaml I am assigning a service account file via secret/volumeMount to server and worker but I don’t see a way yo pass it to orchestrator. Anyone having a similar issue? :')


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["airbyte-platform", "k8s", "helm", "GCS", "job-orchestrator", "service-account", "unauthenticated-user-error"]
2

env vars are getting through, orchestrator is looking for the file but can not find it since it is not attached

3

Did you check the latest docs update https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#external-logs-with-gcs

4

When the guide is followed the extraEnv is never passed to the deployments

5

it worked!!! passed them as env_vars instead and its working fine now, thank you!!

For others, this will add the credentials to workers and the orchestrator but not the server, so just do the same mount to servers and it will be fine

6

Aweesome! Nice to hear Diego!