[x] ReadWriteMany in common-data and deposit-storage will lead to unsupported on default storageClass. I have tried with workaround with nfs, which could be good path
[x] Nimbus 0 after genesis container does not boot properly and stall other clients, which wont be bootstrapped.
kubectl describe pod nimbus-0
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 39m default-scheduler Successfully assigned default/nimbus-0 to gke-eth20-default-pool-0d802a45-pgc2
Normal Pulled 39m kubelet, gke-eth20-default-pool-0d802a45-pgc2 Container image "eth2clients/multinet-nimbus" already present on machine
Normal Created 39m kubelet, gke-eth20-default-pool-0d802a45-pgc2 Created container genesis
Normal Started 39m kubelet, gke-eth20-default-pool-0d802a45-pgc2 Started container genesis
Normal Pulled 38m kubelet, gke-eth20-default-pool-0d802a45-pgc2 Container image "eth2clients/eth2stats-client" already present on machine
Normal Created 38m kubelet, gke-eth20-default-pool-0d802a45-pgc2 Created container eth2stats-client
Normal Started 38m kubelet, gke-eth20-default-pool-0d802a45-pgc2 Started container eth2stats-client
Normal Started 35m (x4 over 38m) kubelet, gke-eth20-default-pool-0d802a45-pgc2 Started container nimbus
Normal Pulled 33m (x5 over 38m) kubelet, gke-eth20-default-pool-0d802a45-pgc2 Container image "eth2clients/multinet-nimbus" already present on machine
Normal Created 33m (x5 over 38m) kubelet, gke-eth20-default-pool-0d802a45-pgc2 Created container nimbus
Warning BackOff 3m55s (x122 over 36m) kubelet, gke-eth20-default-pool-0d802a45-pgc2 Back-off restarting failed container
Error is in several places:
Helm
[x]
ReadWriteMany
incommon-data
anddeposit-storage
will lead to unsupported on default storageClass. I have tried with workaround with nfs, which could be good path[x] Nimbus 0 after genesis container does not boot properly and stall other clients, which wont be bootstrapped.
kubectl describe pod nimbus-0
kubectl get pods
kubectl logs nimbus-0 nimbus