Hello to everyone!! We are deploying Airbyte for the first in our k8s cluster, right now it’s already working in a EC2 docker instance and we wanna migrate our current setup. For that, we deployed the following helm chart using kustomization:

---
apiVersion: <http://kustomize.config.k8s.io/v1beta1|kustomize.config.k8s.io/v1beta1>
kind: Kustomization

helmCharts:
- name: airbyte
  version: 0.42.0
  repo: <https://airbytehq.github.io/helm-charts>
  namespace: airbyte
  releaseName: airbyte

But we wanna add /modify the variables to the existing configuration (like enable the local basic http auth), and we have some questions: • Can I overwrite this file somehow? I saw it’s possible if we have the configMapGenerator enabled and also the

.env

file locally • What happens if I have this local file and I want to have an external db? (using the values for the helm chart it’s possible, but will this overwrite another configuration? Many thanks!!!

• Can I overwrite this file somehow? I saw it’s possible if we have the configMapGenerator enabled and also the

.env

file locally

You should be able to change anything in

values.yaml

and add new variables to it too. The problem comes with updates you can miss some parameters.

• What happens if I have this local file and I want to have an external db? (using the values for the helm chart it’s possible, but will this overwrite another configuration?

Helm will use values from

values.yaml

from where you want to overwrite? I think the BASIC_AUTH_USERNAME is missing from Helm latest version and must be added. @Ramon de la Cruz Ariza do you mind creating a Github issue for that?

@Marcos Marx (Airbyte) / @Ramon de la Cruz Ariza are the BASIC_AUTH_USERNAME / PASSWORD already available in the helm charts? Can't find the setting in the Helm values.yaml

Any news on whether BASIC_AUTH_USERNAME / PASSWORD is usable in the helm chart?

@Saj Dider (Airbyte) Do you know if the request of @Dave Easey and @Ramon de la Cruz Ariza is somwhere on the backlog (adding BASIC_AUTH_USERNAME / PASSWORD already available in the helm charts to the helm charts)? By the way, as a workaround I tried to enable HTTP basic auth on the NGINX controller in Kubernetes, however, the UI isn't loading properly after that, so doesn't seem to work.

Dave and Krisjan the Kubernetes deployments doesn't support the airbyte-proxy container. You can try to change the nginx to enable it OR use a solution to handle access in k8s.

@Marcos Marx (Airbyte) I've tried to add basic auth to the nginx-ingress settings. However, the interface doesn't seem to work / timeout anymore after configuring that (could be that certain front-end API calls can't be made or something?)

@Krisjan Oldekamp did you manage to do this? I have deployed airbyte with helm and want to set some username/pwd and enable authentication tokens

Is there any updates on this? The very helpful slackbot actually tricked me into believing that setting those env variables in values.yaml would work, and even referencing this thread. Theres nothing in the documentation saying that it’s not supported either.

This issue and PR looks to have been aiming to address it, but hasn't had movement for a few months - so I'm assuming there are no updates yet https://github.com/airbytehq/airbyte/issues/17865 https://github.com/airbytehq/airbyte-platform/pull/228