Consul leader electon failures cause pods to be allocated but uncreated #9
Description
Short and sweet:
[root@lb-control-01 ~]# kubectl logs kube-apiserver-lb-control-01 | grep dash
I0721 13:25:14.377336 1 consul.go:241] Storage Error: Unexpected response code: 500, key: registry/controllers/kube-system/kubernetes-dashboard
I0721 13:25:14.544939 1 consul.go:241] Storage Error: Unexpected response code: 500 (rpc error: No cluster leader), key: registry/controllers/kube-system/kubernetes-dashboard
The pod wasn't created:
[root@lb-control-01 ~]# kubectl get pods -a --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system kube-apiserver-lb-control-01 1/1 Running 1 13m
kube-system kube-apiserver-lb-control-02 1/1 Running 0 13m
kube-system kube-apiserver-lb-control-03 1/1 Running 0 13m
kube-system kube-controller-manager-lb-control-02 1/1 Running 0 14m
kube-system kube-podmaster-lb-control-01 2/2 Running 0 13m
kube-system kube-podmaster-lb-control-02 2/2 Running 0 13m
kube-system kube-podmaster-lb-control-03 2/2 Running 0 14m
kube-system kube-proxy-lb-control-01 1/1 Running 0 13m
kube-system kube-proxy-lb-control-02 1/1 Running 0 13m
kube-system kube-proxy-lb-control-03 1/1 Running 0 13m
kube-system kube-proxy-lb-kubeworker-001 1/1 Running 0 13m
kube-system kube-proxy-lb-kubeworker-002 1/1 Running 0 14m
kube-system kube-scheduler-lb-control-02 1/1 Running 0 14m
kube-system kube2consul-lb-control-01 1/1 Running 0 12m
kube-system kube2consul-lb-control-02 1/1 Running 0 14m
kube-system kube2consul-lb-control-03 1/1 Running 0 14m
But I can't create a new one:
[root@lb-control-01 ~]# kubectl create -f /etc/kubernetes/manifests/kubernetes-das>
Error from server: replicationcontrollers "kubernetes-dashboard" already exists
Error from server: Service "kubernetes-dashboard" is invalid: spec.ports[0].nodePort: Invalid value: 30000: provided port is already allocated