0
我们有一个问题,即仪表板的一部分,将永远载入并最终超时交谈端口9090kubernetes仪表盘挂在部署资源
的问题,没有迹象表明在泊坞窗日志仪表盘或kubelet登录主人或工人。
我只好用“--cascade = false”强制删除仪表板的kubectl,因为删除也会挂起。
这是留给我们一个陈旧的副本集通常过期它自己的,但在副本集似乎认为它仍然在使用:
NAMESPACE NAME DESIRED CURRENT READY AGE
kube-system rs/dnsmasq-1410718522 1 1 1 20d
kube-system rs/dnsmasq-autoscaler-1155841093 1 1 1 20d
kube-system rs/grafana-1857700562 1 1 1 17d
kube-system rs/heapster-3338981674 1 1 1 17d
kube-system rs/influxdb-3065341217 1 1 1 17d
kube-system rs/kubedns-3830354952 1 1 1 20d
kube-system rs/kubedns-autoscaler-54374881 1 1 1 20d
kube-system rs/kubernetes-dashboard-head-3335363610 1 1 1 1h
仪表盘从不在国外部署:
NAMESPACE NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
kube-system deploy/dnsmasq 1 1 1 1 20d
kube-system deploy/dnsmasq-autoscaler 1 1 1 1 20d
kube-system deploy/grafana 1 1 1 1 17d
kube-system deploy/heapster 1 1 1 1 17d
kube-system deploy/influxdb 1 1 1 1 17d
kube-system deploy/kubedns 1 1 1 1 20d
kube-system deploy/kubedns-autoscaler 1 1 1 1 20d
kube-system deploy/kubernetes-dashboard 0 0 0 0 1d
经过近一天的仪表板说它没有错误,但很明显,它不是:
kubectl logs kubernetes-dashboard-head-3335363610-v37xz --namespace=kube-system
Using HTTP port: 8443
Creating API server client for https://10.233.0.1:443
Successful initial request to the apiserver, version: v1.5.3+coreos.0
Creating in-cluster Heapster client
Using service account token for csrf signing
来自浏览器:
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "no endpoints available for service \"kubernetes-dashboard\"",
"reason": "ServiceUnavailable",
"code": 503
}
任何主人或工作人员在码头工人都没有仪表板容器。
我们能够让nginx以“--cascade = true”进行重播,并重新部署,但是kubernetes-dashboard和驾驶舱都以相同的方式挂起。