Email Issue in #22

[blackramit]

Hey @leovigna, can't thank you enough for putting together this Helm chart. I'm learning a lot about GKE, K8's, Helm and especially Chainlink... thanks to you!

I too ran into the email issue that was previously reported and resolved it by adding a hard coded email. I was getting: error creating api initializer: Invalid email format.

[blackramit]

Update @leovigna , it seems that bypassing the Email issue with hardcode doesn't work. For some reason the node doesn't recognize the login. Gonna keep banging on this to see if I can figure out the issue. News @11!

[leovigna]

It should be
API_LOGIN: |
example@example.com
Mypassword

[leovigna]

This gets written to a file on /chainlink/.api

[blackramit]

Hey @leovigna , that didn't seem to work. Here's the main part of my variables.yaml

[blackramit]

Also, I jumped into the container with:
kubectl exec -n chainlink -it chainlink-kovan01-0 -c chainlink -- bash

But I didn't find /chainlink/.api

[blackramit]

And in Kubeapps it appears to show up properly, but not sure if this isn't just a reflection of the variables.yaml

[blackramit]

Any suggestions on troubleshooting the deployment and whether the /chainlink/.api is getting loaded properly?

[leovigna]

I think issue might be with more recent versions of chainlink your password needs a specific format. Maybe just test this locally with a docker instance to see if the setup works. Maybe try a password like EXAMPLE_api_password_123!?
Do you have any logs? kubectl logs POD_NAME
It might also be the chart is a bit outdated. I'll look into pushing the latest version I use.