Bootnode container unable to launch _For GoQuorum:_

[ravinayag]

I was following goquorum method to launch the network, while doing bootnode1 was not able to launch its init container and below ref. logs. Pod Status :

quorum        besu-node-bootnode-1-0                                   0/1     Init:0/1    0          4m8s
quorum        besu-node-bootnode-1-pre-install-hook-vbhbn              0/1     Completed   0          4m17s

Configmap :

NAME                                                           DATA   AGE
besu-bootnodes                                                 2      8m59s
besu-node-bootnode-1-address                                   1      8m59s
besu-node-bootnode-1-besu-config                               1      8m55s
goquorum-genesis                                               1      24h
goquorum-node-validator-1-address                              1      24h
goquorum-node-validator-2-address                              1      24h
goquorum-node-validator-3-address                              1      24h
goquorum-node-validator-4-address                              1      24h
goquorum-peers                                                 1      24h

Pod event logs :

  Warning  FailedMount       92s (x11 over 7m44s)  kubelet            MountVolume.SetUp failed for volume "genesis" : configmap "besu-genesis" not found
  Warning  FailedMount       92s (x11 over 7m44s)  kubelet            MountVolume.SetUp failed for volume "static-nodes" : configmap "besu-peers" not found

Expected behaviour : the container should ref. the respective configmap goquorum-genesis and goquorum-peers to mount.

Hence update the helm chart and Readme file, Since this step is missing under For GoQuorum section