Hi guys,

Thank you for fixing prometheus=true fix in chainlink-adapter.
Could you please also bump the version number so it would become available with helm repo update? ;)

The documentation describes the node labeling but the ETH chart does not respect that labeling and it has to be provided manually through the nodeselector value. I think this behavior is unexpected.

I can add it if you want.

Description

Create Eth 2.0 Lightouse Helm Chart to use latest versions & use the new base helm chart.

PS

Create a branch with by commenting /cib command which will alert the create-issue-bot.
Make sure to update the Labels and Projects field of your issue.

Thanks to prepare the helm chart for chainlink, but I met some issues when deploy it.

three issues related to postgresql

1. postgres not found

So this chart doesn't deploy with a postgresql database, and its name has to be postgres

I installed a postgresql pod in same kubernetes cluster, and adjust DNS name to my-release-postgresql.default.svc.cluster.local in values.yaml

2. postgresql password.

I have to manually get the postgresql password and update in values.yaml

3. database chainlink is not exist

I have to manually create a new database chainlink in postgresql container

So finally the DATABASE_URL becomes to

DATABASE_URL: postgresql://postgres:[email protected]:5432/chainlink?sslmode=disable

But there are new problems:

1. WALLET_PASSWORD

the password has several limits, such as 3 capital, 3 small letters, number, more than 12 letters, and so on. So finally I use command uuid to generate the uuid as key and adjust several letters to capital.

abcdE5B07E4B-D704-4100-8DEF-BBD369789E19

2. API_EMAIL

I replace with a fake mailbox.

3. geth issue

% kk logs -f pod/my-release-0
error starting app: dial tcp: lookup geth on 10.96.0.10:53: no such host

I stuck here, not sure how to fix this issue, need help.

update

anyone can give a full installation instruction? Seems I need install another chart eth-geth

but I got same error

Do i have to install all charts in this repo?

update2

this document gives details, looks promose, will follow up

Since medium is not friendly for free user, I download as pdf and upload here.
;One-click Chainlink deployment. Quickly deploy a Chainlink node using… _ by Leo Vigna _ Coinmonks _ Medium.pdf

update3

above url doesn't help a lot, just another way to do helm chart.

I still stuck at the part of geth.

I am trying to create a private network using the chart. I am trying to automate that peers can add each other. Because of which I cannot use the admin.addPeer() command. I need to bootstrap a Bootnode so that each node to connect to the others.
Is it possible to create a Bootnode for a private network using the chart? If so, could you elaborate what are the configuration changes needed to be done for it?
Any other viable solution is also welcome.

Description

Update Chainlink Helm Chart to use latest versions & use the new base helm chart.

PS

Create a branch with by commenting /cib command which will alert the create-issue-bot.
Make sure to update the Labels and Projects field of your issue.

Description

Update Chainlink Helm Chart to use latest versions & use the new base helm chart.

PS

Create a branch with by commenting /cib command which will alert the create-issue-bot.
Make sure to update the Labels and Projects field of your issue.

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.

affinity: {
enabled: false
},
toleration: {
enabled: false
}

It is fixed in the apache/openwhisk repo =>
apache/openwhisk-deploy-kube#606