How to enable keycloak authentication for airbyte using helm chart

To enable Keycloak authentication for Airbyte using Helm chart, you need to follow the steps for deploying Airbyte's Self-Managed Enterprise version. The Keycloak authentication is supported in the Enterprise version of Airbyte. Here are the steps you need to follow: 1. Run the following command to upgrade your instance to Self-Managed Enterprise. If you previously included additional

values

files on your existing deployment, be sure to add these here as well:

bash helm upgrade \   --namespace airbyte \   --values ./values.yaml \   --install [RELEASE_NAME] \   --version [RELEASE_VERSION] \   airbyte/airbyte

2. Once this is complete, you will need to upgrade your ingress to include the new

/auth

path. The following is a skimmed down definition of an ingress resource you could use for Self-Managed Enterprise:

bash apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>   kind: Ingress   metadata:     name: # ingress name, example: enterprise-demo     annotations:       <http://ingress.kubernetes.io/ssl-redirect|ingress.kubernetes.io/ssl-redirect>: "false"   spec:     ingressClassName: nginx     rules:       - host: # host, example: <http://enterprise-demo.airbyte.com|enterprise-demo.airbyte.com>         http:           paths:             - backend:                 service:                   # format is ${RELEASE_NAME}-airbyte-webapp-svc                   name: airbyte-enterprise-airbyte-webapp-svc                   port:                     number: 80 # service port, example: 8080               path: /               pathType: Prefix             - backend:                 service:                   # format is ${RELEASE_NAME}-airbyte-keycloak-svc                   name: airbyte-enterprise-airbyte-keycloak-svc                   port:                     number: 8180               path: /auth               pathType: Prefix             - backend:                 service:                   # format is ${RELEASE_NAME}-airbyte--server-svc                   name: airbyte-enterprise-airbyte-server-svc                   port:                     number: 8001               path: /api/public               pathType: Prefix

After these steps, when you log in, you should expect all connections, sources, and destinations to be present, and configured as prior. Please note that the actual values for

[RELEASE_NAME]

and

[RELEASE_VERSION]

should be replaced with your specific release name and version. For more details, you can refer to the [official Airbyte documentation](https://docs.airbyte.com/enterprise-setup/upgrading-from-community#step-3-deploy-self-managed-enterprise).