问题描述
我在安装kubernetes仪表板时遇到问题。看起来它只是达到待处理状态。我在事件中找到有关由于Docker中的其他映像而导致释放内存的问题的信息。我正在寻找解决方案,无法关闭当前图像。
输出:
{
"kind": "Status","apiVersion": "v1","metadata": {
},"status": "Failure","message": "no endpoints available for service \"kubernetes-dashboard\"","reason": "ServiceUnavailable","code": 503
}
豆荚:
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-f9fd979d6-74xm2 0/1 Pending 0 152m
kube-system coredns-f9fd979d6-q68rg 0/1 Pending 0 152m
kube-system etcd-worker01 1/1 Running 0 152m
kube-system kube-apiserver-worker01 1/1 Running 0 152m
kube-system kube-controller-manager-worker01 1/1 Running 0 152m
kube-system kube-flannel-ds-xhv8x 1/1 Running 0 151m
kube-system kube-proxy-htxxg 1/1 Running 0 152m
kube-system kube-scheduler-worker01 1/1 Running 0 152m
kubernetes-dashboard dashboard-metrics-scraper-7b59f7d4df-b9s6s 0/1 Pending 0 131m
kubernetes-dashboard kubernetes-dashboard-665f4c5ff-md882 0/1 Pending 0 95m
kubernetes-dashboard kubernetes-dashboard-74d688b6bc-rxh4w 0/1 Pending 0 131m
事件:
LAST SEEN TYPE REASON OBJECT MESSAGE
7m54s Warning EvictionThresholdMet node/worker01 Attempting to reclaim ephemeral-storage
2m52s Warning ImageGCFailed node/worker01 (combined from similar events): wanted to free 29893186355 bytes,but freed 0 bytes space with errors in image deletion: [rpc error: code = Unknown desc = Error response from daemon: conflict: unable to delete b4e0de857ea7 (must be forced) - image is being used by stopped container 691fa8251b60,rpc error: code = Unknown desc = Error response from daemon: conflict: unable to delete 172a9481468c (must be forced) - image is being used by stopped container b9e69a358748,...
日志为空。
解决方法
通过执行以下URL授予对仪表板的访问权限:
http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:https/proxy/
注意此部分:
/https:kubernetes-dashboard:https/
如果不添加https,它将不起作用-您将始终得到no endpoints available for service kubernetes-dashboard
。
在此处查看自述文件中的工作链接:kubernetes-dashboard-issue-endpoints。
看看:dashboard-endpoints-issue endpoints-available-for-service-kubernetes-dashboard,dashboard-endpoints,kubernetes-503-no-endpoints-available。
,@PKosiba,不,这不是磁盘问题,这基本上意味着您在集群中的节点/机器上具有所谓的污点和容忍度,这又意味着Kubernetes调度程序无法将Pod调度在任何一个现有节点,因为它没有相应的异味,基本上,您的节点上会有一些东西说“不要在该节点上调度没有此标签disk-pressure的任何东西”:
https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/