Summary
Error occurs when setting authenticationType to credentials in Helm installation, leading to a ‘nil pointer evaluating interface {}.authenticationType’ error.
Question
Hi everyone,
I am currently trying to set up Helm installation using custom values. I already have a running Minio environment that I want to use and I have followed the instructions on the AWS S3 Users migration steps. However, when I am running the installation I am getting error about a “nil pointer evaluating interface {}.authenticationType”
My authenticationType in globals is set to credentials.
Any idea what may be wrong?
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-installation", "authenticationType", "credentials", "nil-pointer-error", "AWS-S3", "Minio"]
Would be great if this could be fixed or if it actually works what would be the configuration scenario to allow external Minio to be used for logging etc.
Thank you
It’s always a good idea to provide links to docs, configuration you used, commands you executed, versions and so on.
Assuming that you followed
https://docs.airbyte.com/deploying-airbyte/integrations/storage
there is a high chance that you might have
storage:
type: "S3"```
Probably this is something you need
```global:
storage:
type: "minio"
endpoint: "..."
storageSecretName: "airbyte-config-secrets"```
When in doubt I recommend checking code of Helm charts directly, because some things might not be documented yet
<https://github.com/airbytehq/helm-charts>
I checked the problem was that the values.yaml that was the template the indentation seems incorrect and I had put the S3 section outside of the storage. Now it worked but I ended up with another issue with the temporal database not being accessible.
Not sure if it reads the properties of the host and credentials from the globals external database or if the problem is the SSL which appears now mandatory for external databases…
Confused with this.
I am quite new to kubernetes so bear with me 
What you mean by checking the helm charts? You mean looking inside the zip files of the helm chart?
Yeah, extracting archive for specific version and checking helm chart code
Indentation in YAML files is super-important, so original helm chart is also useful to check if code indented properly
Yes been trying to check that and figure it out. But even though the UI is already working I am getting issues on the logs still with the S3 configuration.
I seem to have to specify a region for example but on my MinIO installation I dont have any region specified which seems one possible way for causing issues but not sure if its the reason. I have passed in any case in configuration “us-east-1”.
Is there any sample out there than can show how to configure an already existing Minio configuration?
Have you tried this snippet I provided above with some modifications?
I’m not sure if there is anything for that in docs.
My personal approach is checking code and in some cases, some examples can be found with Github search https://github.com/search?q=airbyte+global+storage+minio+endpoint+language%3AYAML&type=code (nothing useful here, but I’m sharing an idea itself)
If I set the storage to Minio it will try to create its own minio instance… so it cannot be minio. In S3 I havent found anything to define the Minio endpoint… so I am not finding a way to configure it. Been going through the Helm in particular for the storage.tpl but dont see the option