bradschauf
commented
7 years ago I noticed that calico is having problems:
kubectl get pods --namespace kube-system
NAME READY STATUS RESTARTS AGE
calico-node-9mhj1 1/2 CrashLoopBackOff 5 4m
calico-policy-controller-3734643172-w9rls 0/1 CrashLoopBackOff 5 4m
configure-calico-n1s7t 0/1 CrashLoopBackOff 5 4m
etcd-kube-master-1 1/1 Running 3 5m
kube-apiserver-kube-master-1 1/1 Running 0 5m
kube-controller-manager-kube-master-1 1/1 Running 0 4m
kube-dns-3913472980-9wjnl 3/3 Running 0 6m
kube-proxy-2v7z2 1/1 Running 0 4m
kube-proxy-4cdr6 1/1 Running 0 6m
kube-scheduler-kube-master-1 1/1 Running 1 5m
kubernetes-dashboard-2396447444-nzbj9 1/1 Running 0 2mkubectl logs calico-node-9mhj1 --namespace kube-system
Error from server (BadRequest): a container name must be specified for pod calico-node-9mhj1, choose one of: [calico-node install-cni]
kubectl logs configure-calico-n1s7t --namespace kube-system
Failed to apply 'ipPool' resource: client: etcd cluster is unavailable or misconfigured; error #0: dial tcp 10.96.232.136:6666: getsockopt: connection refused
kubectl logs calico-policy-controller-3734643172-w9rls --namespace kube-system
2017-04-13 02:24:58,042 6 INFO Configuring /etc/hosts 2017-04-13 02:24:58,042 6 INFO Appended 'kubernetes.default -> 10.96.0.1' to /etc/hosts 2017-04-13 02:24:58,043 6 INFO Beginning execution 2017-04-13 02:24:58,043 6 INFO Leader election enabled? False Traceback (most recent call last): File "
", line 516, in File " ", line 141, in run File "site-packages/pycalico/datastore.py", line 901, in delete_policy_tier File "site-packages/etcd/client.py", line 610, in delete File "site-packages/etcd/client.py", line 860, in wrapper etcd.EtcdConnectionFailed: Connection to etcd failed due to MaxRetryError("HTTPConnectionPool(host='10.96.232.136', port=6666): Max retries exceeded with url: /v2/keys/calico/v1/policy/tier/k8s-network-policy?recursive=true&dir=true (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f907d00a0d0>: Failed to establish a new connection: [Errno 111] Connection refused',))",) controller returned -1
After implementing the fix in #40 I noticed that while the nodes show ready, the dashboard would not function.
I rebuilt the cluster and recreated the dashboard and still get errors when attempting to access the dashboard via the proxy:
Error: 'dial tcp 172.17.0.2:9090: getsockopt: connection refused' Trying to reach: 'http://172.17.0.2:9090/'