Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Kubo 0.7.0 (vSphere): all K8s cluster shut down and then powered up: etcd nodes are in failing state #111
I make this very simple test:
-deploy K8s cluster: OK
-on vCenter, I shut down all those VM
Instance Process State AZ IPs
=> all etcd nodes are in failing state.
ideally, all the nodes should be restarted correctly.
(the workaround to solve this issue is to bosh restart one of the etcd node)
We have created an issue in Pivotal Tracker to manage this:
The labels on this github issue will be updated when the story is started.
found something more interesting:
after all the steps specified above, kubectl get pod provides the following result:
$ kubectl get pod --all-namespaces
kube-dns and dashboard are in CrashLoopBackOff mode
I am also facing this issue. However, in my case if I try to restart the etcd node. I am getting the following error -
14:56:04 | Error: Instance group 'etcd' references an unknown network 'Comp-VM-Net-1'
Started Tue Nov 28 14:56:04 UTC 2017
Any help with this is really appreciated.