Error setting up Airbyte in local kind cluster with default helm values

Summary

The user is facing an error while setting up Airbyte in a local kind cluster using default helm values. The error is related to the authentication type for AWS secrets manager being nil. User has tried setting the value to ‘none’ in values.yaml without success.


Question

Hiya everyone :wave:
I am in the process of setting up Airbyte in my local kind cluster, but the default helm values fail with the following message:


Error: INSTALLATION FAILED: template: airbyte/charts/workload-launcher/templates/deployment.yaml:326:15: executing "airbyte/charts/workload-launcher/templates/deployment.yaml" at <eq ((((.Values.global).secretsManager).awsSecretManager).authenticationType) "credentials">: error calling eq: incompatible types for comparison```
Presumable because `global.secretsManager.awsSecretsManager.authenticationType` is `nil`?
I’ve tried setting this value to `"none"` in various ways in a local values.yaml, but it doesn’t seem to help.
Anyone have any ideas how to get past this?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1727778816175199) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["airbyte", "local-kind-cluster", "helm-values", "aws-secrets-manager", "authentication-type", "values.yaml"]
</sub>
NAME   	NAMESPACE	REVISION	UPDATED                             	STATUS  	CHART        	APP VERSION
airbyte	default  	1       	2024-10-01 12:36:56.383295 +0100 BST	deployed	airbyte-1.0.0	1.0.0
vault  	default  	1       	2024-10-01 12:14:51.916572 +0100 BST	deployed	vault-0.28.1 	1.17.2```
Hmm, that is interesting that `abctl` doesn't do anything special :thinking_face:

well, it does few things extra with kind cluster, volumes, pv, pvc, ingress nginx, but in general it’s a wrapper not magic :unicorn_face:

From a search I see this issue is quite frequently reported. :confused:
I’ve tried using the example values from https://github.com/airbytehq/airbyte-platform/blob/main/charts/airbyte/values.yaml|here, but that hasn’t worked either.

Ideally there should be some boolean that indicates whether you intended to use a secret store at all, which could wrap these templating sections…

why not abctl?
https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart
abctl under the hood creates its own kind cluster

I already have my own kind cluster for local development that includes several services I wish to use as either sources or destinations

I’m just trying to evaluate airbyte locally before deciding whether to move forward with an installation into our cloud infra.

If I could see the values.yaml that abctl uses that would probably help…

So, I managed to work around it.
I assumed that some secret store was required, so I just did a helm install of hashicorp vault.
I found <https://github.com/airbytehq/airbyte-platform/blob/main/configs/airbyte.sample.yml|this config file example> in the repo and used the secretsManager: block there to configure my values correctly.
Annoyingly, even though I chose to use vault, I still had to have the secretsManager.awsSecretsManager.authenticationType key present for the template to generate without error :shrug:

What do you get for helm ls when it comes to Airbyte?

this is my output for abctl deployment

NAME          NAMESPACE     REVISION  UPDATED                               STATUS    CHART                 APP VERSION
airbyte-abctl airbyte-abctl 1         2024-09-26 13:02:39.073554 +0200 CEST deployed  airbyte-1.0.0         1.0.0```

It looks like abctl sets some values by default https://github.com/airbytehq/abctl/blob/6e6dfe45fc25d631d7b684f2fd887f17c07fcebf/internal/cmd/local/local/install.go#L183-L188|install.go#L183-L188, but not many of them. The rest comes from default values.yaml