我在上传kubernetes仪表板时遇到了问题。它看起来只会达到挂起状态。我在事件中找到了关于由于docker中的其他图像而导致的内存释放问题的信息。我正在寻找解决方案,我不能关闭当前的图像。
输出:
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {
},
"status": "Failure",
"message": "no endpoints available for service \"kubernetes-dashboard\"",
"reason": "ServiceUnavailable",
"code": 503
}pods:
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,...日志是空的。
发布于 2020-10-14 18:49:16
通过执行以下URL授予对dashbord的访问权限:
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-issueendpoints-available-for-service-kubernetes-dashboard,dashboard-endpoints,kubernetes-503-no-endpoints-available。
发布于 2020-10-14 21:31:49
@PKosiba,不,这不是磁盘问题,这基本上意味着你在集群中的节点/机器上有所谓的污染和容错,这反过来意味着Kubernetes scheduler无法在任何现有节点上调度你的pod,因为它没有相应的污染,基本上你在你的节点上有一些东西,上面写着“不要在这个节点上调度任何没有这个标签disk-pressure的东西”:
https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/
https://stackoverflow.com/questions/64349844
复制相似问题