https://linen.dev logo
Join Slack
Powered by
Hi all, we're using helm charts to deploy airbyte....
# replication-troubleshooting
e
Hi all, we're using helm charts to deploy airbyte. We have an issue with 
airbyte webapp
where the deployment ignores serviceAccount. We have 
global.serviceAccountName
as well as
Copy code
serviceAccount:
  create: false
  name:..
and everything's ok for every other pod except webapp. If I view resource description I still see 
serviceAccountName: default
while for others I can see the values we've provided. We're using the service account to load secrets from Google Secret Manager (by attaching a volume) and would prefer to not have them hardcoded anywhere as it makes secret lifecycle much simpler for us. Is there anything we can do?
✍️ 1
submitted a pull request, let me know if I should change something or close it: https://github.com/airbytehq/airbyte/pull/18151
k
global.serviceAccountName
has higher priority since it’s an YAML anchor for 
serviceAccount.name
So when you’re setting 
global.serviceAccountName
you’re also setting 
serviceAccount.name
And I’m not sure if webapp actually need this one, since it’s basically nginx that serves static content(i.e it has only 3 vars by default)
Or you’re deploying sidecar alongside the webapp?
e
Does webapp access postgres server?
k
Nope
It does requests to server and then server does the access to postgres
e
oh, then it doesn't need it, I'll close the pull-request. We werent' sure which of the pods need to access secrets required for postgres login.
k
But I think I’ll merge PR anyways
e
alright, thank you for fast response!
k
since if someone will want to deploy a sidecar then it potentially could be an issue
👍 1
as for the pods that need access to DB you can check values.yaml of every subchart
there should be an env_vars block that has documented a set of default env vars for each component
This also should be available in airbyte values.yaml but not sure
e
alright, thanks
u
@[DEPRECATED] Marcos Marx turned this thread into Zendesk ticket 2923 to ensure timely resolution!
s
Thanks for raising your issue. Feel free to post more questions here on Slack @Emilja Dankevičiūtė!
Open in Slack
PreviousNext
Powered by