Summary
User is seeking simple Helm charts for deploying Airbyte v1.2.0 on Kubernetes without Keycloak, preferring basic authentication.
Question
hello team,
Does anyone helm-charts ready for deploying airbyte v1.2.0 in k8s?
I want something basic for setup , no need for keycloak, want to keep basic auth if that’s possible.
I have already pulled charts from bitnami that that’s too complicated, if someone do have clean charts that has been deployed and its functional I would really appreciate if you can share with me 
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
['helm-charts', 'airbyte-v1.2.0', 'kubernetes', 'basic-auth']
Looking for a basic setup to go , and than later I can add things that I need.
What’s wrong with default deployment?
https://docs.airbyte.com/deploying-airbyte/
“basic” setup will be different for everybody and you customize it with values.yaml
What you mentioned seems like few lines in values.yaml
auth:
enabled: true
keycloak:
enabled: false```
You haven't mentioned if you are going to run it on any cloud or your own k8s
Running in EKS, Iam trying to setup 1.2.0 .
On the helm charts Iam pulling for that, values.yaml are pretty long.
Iam not familiar wiht all those stuff like: connector-builder-server or connector-rollout-worker , I havent met those in v0…
Looking for a basic setup to go , and than later I can add things that I need.
What’s wrong with default deployment?
https://docs.airbyte.com/deploying-airbyte/
“basic” setup will be different for everybody and you customize it with values.yaml
What you mentioned seems like few lines in values.yaml
auth:
enabled: true
keycloak:
enabled: false```
You haven't mentioned if you are going to run it on any cloud or your own k8s
Running in EKS, Iam trying to setup 1.2.0 .
On the helm charts Iam pulling for that, values.yaml are pretty long.
Iam not familiar wiht all those stuff like: connector-builder-server or connector-rollout-worker , I havent met those in v0…