https://linen.dev logo
Join Slack
Powered by
Hi everyone! I’ve got a small question regarding t...
# replication-ask-ai
j
Hi everyone! I’ve got a small question regarding the documentation around running Airbyte Open Source on Kubernetes. As stated here the recommended way to configure Airbyte on K8s is going via Kustomize overlays to setup env variables. But at the same time the docs says that Kustomize is deprecated since version 0.40. All I really want to do is figure out how to enable basic authentication on a Helm deployment. Can I do this by setting the BASIC_AUTH_*-variables as noted here in my 
values.yaml
?
k
A message from kapa.ai
New message text here
j
Thanks, @kapa.ai! You are both very helpful and a bit scary at the same time. I think I love you for it.
k
A message from kapa.ai
New message text here
j
Well, as a closing remark it turns out that @kapa.ai is wrong since those env variables isn’t yet supported in a Helm deployment. This is not documented but is mentioned in the thread that the slackbot is referencing.
k
A message from kapa.ai
I apologize for any confusion earlier. You're correct that some environment variables might not be directly supported in a Helm deployment. In such cases, you can try using the 
extraEnv
key in the Helm chart to set additional environment variables. However, this might not cover all use cases, and some manual adjustments might be necessary. For more information on configuring Airbyte, you can refer to the [Configuring Airbyte documentation](https://docs.airbyte.com/operator-guides/configuring-airbyte). If you encounter any issues or need further assistance, feel free to ask, and I'll do my best to help based on the available information extracts.
j
I use like this, I have it in both 
global
and 
webapp
. Probably it will work by having it in just one of them. You can have all in one secret, or in multiple secrets, as long you don’t have it in the secret airbyte creates in deployment (deploymentMode = oss will always recreate it and you’ll lose your changes). I use terraform to create the secrets (getting values from vault), but you can also create the secrets manually (OpenLens for example) or programmatically. For production consider using oauth2-proxy (also possible through Helm Chart here).
Untitled.yaml
❤️ 1
j
Great! Thanks for the input, @Jefferson Roth! Will read up on oauth2-proxy.
j
It’s also possible to have both: • oauth2 for human users (using OKTA or any other sso option) • basic auth for programmatic tools (for example to create sources and destinations via terraform). You’ll need a secret for it.
Open in Slack
PreviousNext
Powered by