[英]Unable to access Kubernetes Dashboard panel (503 no endpoints available)
我在放置 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,因為它沒有相應的污點,基本上你的節點上有一些東西說“不要在這個沒有這個標簽磁盤壓力的節點上安排任何事情”:
https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.