Hi ! 🙂 Is it possible to not hardcore

airbyte-admin

here but take the value in configuration ? I have not the same name for the

serviceAccountName

attribute… 😕 impossible to launch sync https://github.com/airbytehq/airbyte/blob/2a3817748aca2e0db30f7ba42ba9bf4e9f893105[…]ava/io/airbyte/workers/process/AsyncOrchestratorPodProcess.java

Hello Benjamin Danies, it's been a while without an update from us. Are you still having problems or did you find a solution?

Hello @Sajarin Dider still have the issue : Due to our kubernetes config / secrets management we changed the admin service account name from

airbyte-admin

to

airbyte

(https://github.com/airbytehq/airbyte/blob/v0.40.29/kube/resources/admin-service-account.yaml). The main issue here is the service account seems to be hardcoded in few java files (like here : https://github.com/airbytehq/airbyte/blob/v0.40.29/airbyte-commons-worker/src/main[…]ava/io/airbyte/workers/process/AsyncOrchestratorPodProcess.java)

Hey Benjamin, Apologies for the lack of response, I didn't see these messages. I believe it is possible to change the airbyte-admin value but you will have to do some significant refactoring. Is there a particular use case you're trying to achieve?

The serviceAccountName is provided by another service in my company (devOps) they created the serviceAccountName

airbyte

not

airbyte-admin

This is for helm deploys, but there seems to be an .env value here which you can modify: https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte/values.yaml#L8 I'm not sure if this would work for your deployment though.

maybe, we still use an (not very) old aibyte version with kustomize. It’s not possible anymore, so we’ll check again using helm 🙂

Thanks for your question!