ethpandaops / ethereum-helm-charts Goto Github PK

Hello, is there any plan to bump the skylenet/blockscout image to use a more recent blockscout version here: https://github.com/blockscout/blockscout/releases?

Publishing the index messed up and 0.1.1 is not in the yaml file

Seeing this trying to run reth 0.0.13 once it gets to execution

 

2024-02-20T20:09:10.044000Z  INFO reth 0.1.0-alpha.19 (6dc30b4) starting |  
-- | --
  |   | /app/bin/reth/src/builder.rs:460:14 |  
  |   | Location: |  
  |   |   |  
  |   |   |  
  |   | 1: invalid type: map, expected a duration |  
  |   | 1:    \| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |  
  |   | 1: 26 \| [stages.execution.max_duration] |  
  |   | 1:    \| |  
  |   | 1: TOML parse error at line 26, column 1 |  
  |   | 0: Bad TOML data |  
  |   | Caused by: |  
  |   |   |  
  |   | Error: Could not load config file "/data/config.toml"

Nothing special about how we're initializing the pod or anything with Helm, just normal install of the chart.

values:

        persistence:
          enabled: true
          size: 3Ti
          storageClassName: gp3
        serviceMonitor:
          enabled: true
          namespace: monitoring
          labels:
            instance: primary
          path: /metrics

When configuring ingress for the nethermind helm chart version 0.3.4 I get this error
error calling include: template: no template \"nethermind.httpPort\" associated with template \"gotpl\"\n", "stderr_lines": ["Error: UPGRADE FAILED: template: nethermind/templates/ingress.yaml:3:16: executing \"nethermind/templates/ingress.yaml\" at <i
I was looking at it and it seems that it's because this line is still there in the ingress template https://github.com/ethpandaops/ethereum-helm-charts/blob/nethermind-0.2.0/charts/nethermind/templates/ingress.yaml#L3 but this line has been removed from the helpers template .https://github.com/ethpandaops/ethereum-helm-charts/blob/nethermind-0.2.0/charts/nethermind/templates/_helpers.tpl#L72

I could add a quick PR to fix :)

https://github.com/ConsenSys/web3signer/tree/master/helm/web3signer

I'm currently exploring running a private network using Erigon, but I'm encountering some challenges. Could someone provide guidance or a step-by-step tutorial on how to set up and run an Erigon private network?

Specifically, I'm looking for details on:

1. Installation: How to install Erigon and any prerequisites.
2. Configuration: Guidance on configuring Erigon for a private network setup.
3. Genesis Block: Steps to create a genesis block for the private network.
4. Running the Network: Instructions on starting and managing the private network.
5. Troubleshooting: Common issues that might arise and how to resolve them.

Any additional tips, best practices, or resources would also be greatly appreciated. Thank you in advance for your assistance!

Make a helm chart for https://github.com/pk910/light-beaconchain-explorer

In at least three of the client charts (lighthouse, besu, and nethermind), the default listen address is 0.0.0.0. This causes issues for single stack (or IPv6-first dual stack) environments.

The fix here is to update the defaults to :: instead of 0.0.0.0. From my research the global IPv6 address covers IPv4 as well, but there may be cases where this is not true. Today, one can override the command template in each chart to fix this, but it's fragile and prone to breakage from future chart updates.

E.g. I added --JsonRpc.EngineHost='::' for Nethermind.

https://github.com/sifraitech/grandine

Hey just wondering when you will update your dockerhub prysm image to version 4.0.8

Best regards

I am getting the following error with reth chart 0.0.6 and kubernetes 1.27

      .spec.template.spec.containers[name="reth"].ports: duplicate entries for key [containerPort=8545,protocol="TCP"]
      .spec.template.spec.containers[name="reth"].ports: duplicate entries for key [containerPort=8551,protocol="TCP"]

Passing the following values fixes it:

          httpPort: 8544,
          authPort: 8550,

However, the default values.yaml should be valid. Thanks in advance

uses log.directory, should use --log.file.directory

Make a helm chart for tx fuzzer

reth service monitor claims there's a service with named ports metrics

This does not exist on the Service

https://github.com/wmitsuda/otterscan

Currently just the dshackle chart has this as per #114

We should add this convention to all other charts.

I cannot set new gaslimit on geth, it default is 5000
{ difficulty: 17179869184, extraData: "0x11bbe8db4e347b4e8c937c1c8370e4b5ed33adb3db69cbdb7a38e1e50b1b82fa", gasLimit: 5000, gasUsed: 0, hash: "0xd4e56740f876aef8c010b86a40d5f56745a118d0906a34e69aec8c0db1cb8fa3", logsBloom: "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000", miner: "0x0000000000000000000000000000000000000000", mixHash: "0x0000000000000000000000000000000000000000000000000000000000000000", nonce: "0x0000000000000042", number: 0, parentHash: "0x0000000000000000000000000000000000000000000000000000000000000000", receiptsRoot: "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421", sha3Uncles: "0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347", size: 540, stateRoot: "0xd7f8974fb5ac78d9ac099b9ad5018bedc2ce0a72dad1827a1709da30580f0544", timestamp: 0, totalDifficulty: 17179869184, transactions: [], transactionsRoot: "0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421", uncles: [] }

I receive this error: W0625 16:36:25.287004 724352 warnings.go:70] spec.template.spec.containers[0].ports[3]: duplicate port definition with spec.template.spec.containers[0].ports[2]

when using the "geth.enabled.true" and "lighthouse.enabled.true" configuration on the ethereum-node umbrella chart. if i set the wsPort to say 8546 for geth, then the warning goes away.

i think that maybe we could either rename the port to http-ws-port if they are the same, or just use a different port for each.

PS: willing to take this issue.

To avoid naming collisions when deploying charts with the same names accross multiple namespaces.

Hi, i checked out your genesis generator and it looks like you still have clique settings in it. What about proof of stake?

https://github.com/emeraldpay/dshackle

By default, horizontally scalable with shared Redis instance.

Hi,

In your chart "ipfs-cluster", we can't add more labels to the cluster pod (statefulset).
It would be nice to have the possibility to add more labels.

For example, I want to add prometheus labels to auto scrape the metrics. Impossible now if I don't use selector labels (they are shared with the ipfs pod, that can't be monitored so can't use selector labels).

It would be nice to have a way of providing a launchpad https://launchpad.ethereum.org/en/

Add a helm chart of: https://github.com/ethpandaops/json_rpc_snoop