taiko-helm-charts

ethereum-node

This chart acts as an umbrella chart and allows to run a ethereum execution and consensus layer client. It’s also able to deploy optional monitoring applications.

Homepage: https://ethereum.org

Source Code

• https://github.com/ethpandaops/ethereum-helm-charts

Subcharts

| Repository | Name | Version | |————|——|———| | file://../besu | besu | 1.0.7 | | file://../erigon | erigon | 1.0.10 | | file://../ethereum-metrics-exporter | ethereum-metrics-exporter | 0.1.4 | | file://../ethereumjs | ethereumjs | 0.0.8 | | file://../geth | geth | 1.0.8 | | file://../grandine | grandine | 0.1.2 | | file://../lighthouse | lighthouse | 1.1.3 | | file://../lodestar | lodestar | 1.1.3 | | file://../nethermind | nethermind | 1.0.12 | | file://../nimbus | nimbus | 1.1.3 | | file://../prysm | prysm | 1.1.4 | | file://../reth | reth | 0.0.14 | | file://../teku | teku | 1.1.3 | | file://../tracoor-agent | tracoor-agent | 0.0.1 | | file://../xatu-sentry | xatu-sentry | 0.0.8 |

Details

Ideally you should have a look at the default values.yaml to get a better understanding on how this chart works.

Pre-defined networks

The following networks are built into the chart and can be configured by just setting the global.main.network variable:

• mainnet
• sepolia
• holesky

Consensus layer checkpoint sync

The chart also has pre-defined checkpoint sync endpoints for each one of the built in networks. By default, the chart will be using these. You can disable this by setting global.checkpointSync to false.

global:
  checkpointSync:
    enabled: true
    addresses:
      mainnet: https://mainnet-checkpoint-sync.attestant.io
      sepolia: https://checkpoint-sync.sepolia.ethpandaops.io
      holesky: https://checkpoint-sync.holesky.ethpandaops.io

Choosing the execution and consensus layer software

For the consensus layer node, you can choose between lighthouse, lodestar, teku, prysm or lighthouse. To enable one of them, you’ll need to set the clients enabled var to true. For example:

lighthouse:
  enabled: true

For the execution layer node you can choose between besu, ,erigon, geth or nethermind. To enable one of them you follow the same approach as before:

geth:
  enabled: true

Note: You should not enable multiple CL/EL nodes. The chart only works if you enable 1 EL and 1 CL node.

Complete example

Run lighthouse/geth combo on the Sepolia network with metrics-exporter enabled:

##
## $ helm install holesky-lighthouse-geth-0 ethereum-helm-charts/ethereum-node -f values.yaml
##

global:
  main:
    network: holesky
  checkpointSync:
    enabled: true

# Client pairs
geth:
  enabled: true
lighthouse:
  enabled: true

# Monitoring
ethereum-metrics-exporter:
  enabled: true

This site is open source. Improve this page.