search

luxas / kubeadm-workshop

Showcasing a bare-metal multi-platform kubeadm setup with persistent storage and monitoring
MIT License
680 stars 190 forks source link

timeout for kubectl top nodes #18

Open gongysh2004 opened 7 years ago

gongysh2004 commented 7 years ago

could you please help me to see why it is timeout to run top nodes?

thanks

ubuntu@kubernetes-1:~/kubeadm-workshop/demos/loadbalancing$ kubectl -n kube-system get svc NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE elasticsearch 10.105.139.213 9200/TCP 13h heapster 10.102.145.188 80/TCP 1h kibana 10.107.223.233 5601:31601/TCP 13h kube-dns 10.96.0.10 53/UDP,53/TCP 21h kubernetes-dashboard 10.99.5.191 80:30006/TCP 7h monitoring-influxdb 10.109.34.172 8086/TCP 1h weave-scope-app 10.98.112.99 80:30005/TCP 7h

ubuntu@kubernetes-1:~/kubeadm-workshop/demos/loadbalancing$ kubectl -n kube-system get po NAME READY STATUS RESTARTS AGE elasticsearch-3501859570-tftrz 1/1 Running 0 13h etcd-kubernetes-1 1/1 Running 1 21h fluentd-gpnkj 1/1 Running 83 13h fluentd-j6r9h 1/1 Running 1 13h heapster-57121549-gq72j 1/1 Running 0 1h kibana-3301510243-5zgd3 1/1 Running 0 13h kube-apiserver-kubernetes-1 1/1 Running 0 21h kube-controller-manager-kubernetes-1 1/1 Running 0 21h kube-dns-692378583-tnz59 3/3 Running 0 21h kube-flannel-ds-680qc 2/2 Running 2 13h kube-flannel-ds-flm3p 2/2 Running 0 13h kube-flannel-ds-v5j8d 2/2 Running 0 21h kube-proxy-6tsn9 1/1 Running 0 13h kube-proxy-f3g0b 1/1 Running 0 21h kube-proxy-h018q 1/1 Running 0 13h kube-scheduler-kubernetes-1 1/1 Running 0 21h kubernetes-dashboard-2039414953-129cd 1/1 Running 0 7h monitoring-influxdb-3480804314-9z3zz 1/1 Running 0 1h weave-scope-agent-1d6w2 1/1 Running 0 7h weave-scope-agent-1jwd7 1/1 Running 0 7h weave-scope-agent-kq7zd 1/1 Running 0 7h weave-scope-app-879505699-h03l6 1/1 Running 0 7h

ubuntu@kubernetes-1:~/kubeadm-workshop/demos/monitoring$ kubectl top nodes --heapster-port=80 Error from server (ServerTimeout): the server cannot complete the requested operation at this time, try again later (get services http:heapster:80)

luxas commented 7 years ago

Why do you use --heapster-port=80? What does the heapster logs say?