Command options as k8s ConfigMap?

[khteh]

This should only be used in very rare cases e.g. if you are not 100% sure if something is a bug or asking a question that leads to improving the documentation. For general questions please use discord or the Ethereum stack exchange at https://ethereum.stackexchange.com.

How to configure all the command options as k8s ConfigMap?

    spec:
      containers:
        - name: geth
          image: ethereum/client-go:v1.14.12
          imagePullPolicy: Always
          args:
            - --holesky
            - --http
            - --http.addr=0.0.0.0
            - --http.vhosts=geth
            - --ws
            - --ws.addr=0.0.0.0
            - --authrpc.jwtsecret=/tmp/jwtsecret
            - --datadir=/data

I would love these to be organized into ConfigMap instead of in the STS manifest file.

[skylenet]

hey @khteh . I think this is not the right repo to have that conversation. The go-ethereum team doesn't have any official instructions on how to run geth on kubernetes. My team has some helm charts available (including one for geth): https://github.com/ethpandaops/ethereum-helm-charts , feel free to use them if you like. You're welcome to create kubernetes specific issues/questions on our repo there.

[MariusVanDerWijden]

Thanks @skylenet for weighing in here, will close this issue for now. Thanks for reporting

[khteh]

Do you have a sample .toml file used with --config for all the command line options in https://github.com/ethpandaops/ethereum-helm-charts/blob/master/charts/geth/values.yaml?