Tomasz Wija
09/23/2024, 11:43 PMuser
09/23/2024, 11:44 PMvalues.yml
file. Ensure instance-admin-email
and instance-admin-password
are all available via Kubernetes Secrets. Here is a sample configuration from the [Airbyte documentation](https://docs.airbyte.com/enterprise-setup/implementation-guide#step-2-configure-your-deployment): yaml global: edition: enterprise airbyteUrl: # e.g. <https://airbyte.company.example> auth: instanceAdmin: firstName: ## First name of admin user. lastName: ## Last name of admin user. identityProvider: type: oidc secretName: airbyte-config-secrets ## Name of your Kubernetes secret. oidc: domain: ## e.g. company.example appName: ## e.g. airbyte display-name: ## e.g. Company SSO - optional, falls back to appName if not provided clientIdSecretKey: client-id clientSecretSecretKey: client-secret
2. If you have deployed to your own Kubernetes cluster using Helm, you can view your credentials by running the following command: bash kubectl get secret airbyte-auth-secrets -n <YOUR_NAMESPACE> -o yaml
3. If you wish to turn off authentication, you can do so by adding the following to your values.yaml
file: yaml global: auth: enabled: false
4. If you're still facing issues, it might be due to a bug or an issue with the specific version of the Helm chart you're using. You can check the [Airbyte Github issues](https://github.com/airbytehq/airbyte/issues) for any known problems or report a new one. Remember to replace the placeholders with your actual values. If you're still having trouble, please provide more details or error messages you're encountering for further assistance.