kubernetes仪表板错误:“度量标准客户端运行状况检查失败:服务器找不到请求的资源(获取服务heapster)." [英] kubernetes dashboard error : 'Metric client health check failed: the server could not find the requested resource (get services heapster).'
本文介绍了kubernetes仪表板错误:“度量标准客户端运行状况检查失败:服务器找不到请求的资源(获取服务heapster)."的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我是kubernetes世界的新手，所以如果我写错了，请原谅我.我正在尝试部署kubernetes仪表板
I'm new in kubernetes world, so forgive me if i'm writing mistake. I'm trying to deploy kubernetes dashboard
为了将仪表板安装到主节点上，我的集群包含三个主节点和3个排空且无法调度的工作线程:
My cluster is containing three masters and 3 workers drained and not schedulable in order to install dashboard to masters nodes :
[root@pp-tmp-test20 ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
pp-tmp-test20 Ready master 2d2h v1.15.2
pp-tmp-test21 Ready master 37h v1.15.2
pp-tmp-test22 Ready master 37h v1.15.2
pp-tmp-test23 Ready,SchedulingDisabled worker 36h v1.15.2
pp-tmp-test24 Ready,SchedulingDisabled worker 36h v1.15.2
pp-tmp-test25 Ready,SchedulingDisabled worker 36h v1.15.2
我正在尝试通过以下URL部署kubernetes仪表板:
I'm trying to deploy kubernetes dashboard via this url :
[root@pp-tmp-test20 ~]# kubectl create -f https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.1/src/deploy/recommended/kubernetes-dashboard.yaml
-
此后，在我的主节点
pp-tmp-test20/172.31.68.220豆荚
kube-system kubernetes-dashboard-5698d5bc9-ql6q8 /1 Running 1 7m11s 10.244.0.7 pp-tmp-test20 <none> <none>- 豆荚的日志
[root@pp-tmp-test20 ~]# kubectl logs kubernetes-dashboard-5698d5bc9-ql6q8 -n kube-system 2019/08/14 10:14:57 Starting overwatch 2019/08/14 10:14:57 Using in-cluster config to connect to apiserver 2019/08/14 10:14:57 Using service account token for csrf signing 2019/08/14 10:14:58 Successful initial request to the apiserver, version: v1.15.2 2019/08/14 10:14:58 Generating JWE encryption key 2019/08/14 10:14:58 New synchronizer has been registered: kubernetes-dashboard-key-holder-kube-system. Starting 2019/08/14 10:14:58 Starting secret synchronizer for kubernetes-dashboard-key-holder in namespace kube-system 2019/08/14 10:14:59 Initializing JWE encryption key from synchronized object 2019/08/14 10:14:59 Creating in-cluster Heapster client 2019/08/14 10:14:59 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds. 2019/08/14 10:14:59 Auto-generating certificates 2019/08/14 10:14:59 Successfully created certificates 2019/08/14 10:14:59 Serving securely on HTTPS port: 8443 2019/08/14 10:15:29 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds. 2019/08/14 10:15:59 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.- 吊舱的描述
[root@pp-tmp-test20 ~]# kubectl describe pob kubernetes-dashboard-5698d5bc9-ql6q8 -n kube-system Name: kubernetes-dashboard-5698d5bc9-ql6q8 Namespace: kube-system Priority: 0 Node: pp-tmp-test20/172.31.68.220 Start Time: Wed, 14 Aug 2019 16:58:39 +0200 Labels: k8s-app=kubernetes-dashboard pod-template-hash=5698d5bc9 Annotations: <none> Status: Running IP: 10.244.0.7 Controlled By: ReplicaSet/kubernetes-dashboard-5698d5bc9 Containers: kubernetes-dashboard: Container ID: docker://40edddf7a9102d15e3b22f4bc6f08b3a07a19e4841f09360daefbce0486baf0e Image: k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1 Image ID: docker-pullable://k8s.gcr.io/kubernetes-dashboard-amd64@sha256:0ae6b69432e78069c5ce2bcde0fe409c5c4d6f0f4d9cd50a17974fea38898747 Port: 8443/TCP Host Port: 0/TCP Args: --auto-generate-certificates State: Running Started: Wed, 14 Aug 2019 16:58:43 +0200 Last State: Terminated Reason: Error Exit Code: 1 Started: Wed, 14 Aug 2019 16:58:41 +0200 Finished: Wed, 14 Aug 2019 16:58:42 +0200 Ready: True Restart Count: 1 Liveness: http-get https://:8443/ delay=30s timeout=30s period=10s #success=1 #failure=3 Environment: <none> Mounts: /certs from kubernetes-dashboard-certs (rw) /tmp from tmp-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from kubernetes-dashboard-token-ptw78 (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: kubernetes-dashboard-certs: Type: Secret (a volume populated by a Secret) SecretName: kubernetes-dashboard-certs Optional: false tmp-volume: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium: SizeLimit: <unset> kubernetes-dashboard-token-ptw78: Type: Secret (a volume populated by a Secret) SecretName: kubernetes-dashboard-token-ptw78 Optional: false QoS Class: BestEffort Node-Selectors: dashboard=true Tolerations: node-role.kubernetes.io/master:NoSchedule node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 2m41s default-scheduler Successfully assigned kube-system/kubernetes-dashboard-5698d5bc9-ql6q8 to pp-tmp-test20.tec.prj.in.phm.education.gouv.fr Normal Pulled 2m38s (x2 over 2m40s) kubelet, pp-tmp-test20 Container image "k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1" already present on machine Normal Created 2m37s (x2 over 2m39s) kubelet, pp-tmp-test20 Created container kubernetes-dashboard Normal Started 2m37s (x2 over 2m39s) kubelet, pp-tmp-test20 Started container kubernetes-dashboard- 仪表板服务的描述
[root@pp-tmp-test20 ~]# kubectl describe svc/kubernetes-dashboard -n kube-system Name: kubernetes-dashboard Namespace: kube-system Labels: k8s-app=kubernetes-dashboard Annotations: <none> Selector: k8s-app=kubernetes-dashboard Type: ClusterIP IP: 10.110.236.88 Port: <unset> 443/TCP TargetPort: 8443/TCP Endpoints: 10.244.0.7:8443 Session Affinity: None Events: <none>- 我的主机上运行吊舱的docker ps
[root@pp-tmp-test20 ~]# Docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 40edddf7a910 f9aed6605b81 "/dashboard --inse..." 7 minutes ago Up 7 minutes k8s_kubernetes-dashboard_kubernetes-dashboard-5698d5bc9-ql6q8_kube-system_f785d4bd-2e67-4daa-9f6c-19f98582fccb_1 e7f3820f1cf2 k8s.gcr.io/pause:3.1 "/pause" 7 minutes ago Up 7 minutes k8s_POD_kubernetes-dashboard-5698d5bc9-ql6q8_kube-system_f785d4bd-2e67-4daa-9f6c-19f98582fccb_0 [root@pp-tmp-test20 ~]# docker logs 40edddf7a910 2019/08/14 14:58:43 Starting overwatch 2019/08/14 14:58:43 Using in-cluster config to connect to apiserver 2019/08/14 14:58:43 Using service account token for csrf signing 2019/08/14 14:58:44 Successful initial request to the apiserver, version: v1.15.2 2019/08/14 14:58:44 Generating JWE encryption key 2019/08/14 14:58:44 New synchronizer has been registered: kubernetes-dashboard-key-holder-kube-system. Starting 2019/08/14 14:58:44 Starting secret synchronizer for kubernetes-dashboard-key-holder in namespace kube-system 2019/08/14 14:58:44 Initializing JWE encryption key from synchronized object 2019/08/14 14:58:44 Creating in-cluster Heapster client 2019/08/14 14:58:44 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds. 2019/08/14 14:58:44 Auto-generating certificates 2019/08/14 14:58:44 Successfully created certificates 2019/08/14 14:58:44 Serving securely on HTTPS port: 8443 2019/08/14 14:59:14 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds. 2019/08/14 14:59:44 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds. 2019/08/14 15:00:14 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.1/在我的主服务器上，我启动代理服务器
1/ On my master I start the proxy
[root@pp-tmp-test20 ~]# kubectl proxy Starting to serve on 127.0.0.1:80012/我从主服务器启动带有x11重定向的firefox，并点击了该网址
2/ I launch firefox with x11 redirect from my master and hit this url
http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#!/login这是我在浏览器中收到的错误消息
this is the error message I get in the browser
Error: 'dial tcp 10.244.0.7:8443: connect: no route to host' Trying to reach: 'https://10.244.0.7:8443/'与此同时，我从启动代理的控制台收到了这些错误
In the same time i got these errors from the console where I launched the proxy
I0814 16:10:05.836114 20240 log.go:172] http: proxy error: context canceled I0814 16:10:06.198701 20240 log.go:172] http: proxy error: context canceled I0814 16:13:21.708190 20240 log.go:172] http: proxy error: unexpected EOF I0814 16:13:21.708229 20240 log.go:172] http: proxy error: unexpected EOF I0814 16:13:21.708270 20240 log.go:172] http: proxy error: unexpected EOF I0814 16:13:39.335483 20240 log.go:172] http: proxy error: context canceled I0814 16:13:39.716360 20240 log.go:172] http: proxy error: context canceled但是刷新n次(随机)后，浏览器我可以访问登录界面以输入令牌(之前创建)
but after refresh n times (randomly) the browser I'm able to reach the login interface to enter the token (created before)
但是...再次发生相同的错误
But... the same error occur again
点击n次登录"按钮后，我可以获取仪表板..几秒钟.
After hit n times the 'sign in' button I'm able to get the dashboard.. for few seconds.
之后，当我浏览界面时，仪表板开始产生相同的错误:
after that the dashboard start to produce the same errors when I'm am exploring the interface:
我查看了pod日志，我们可以看到一些流量:
I looked the pod logs, we can see some trafic :
[root@pp-tmp-test20 ~]# kubectl logs kubernetes-dashboard-5698d5bc9-ql6q8 -n kube-system 2019/08/14 14:16:56 Getting list of all services in the cluster 2019/08/14 14:16:56 [2019-08-14T14:16:56Z] Outcoming response to 10.244.0.1:56140 with 200 status code 2019/08/14 14:17:01 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds. 2019/08/14 14:17:22 [2019-08-14T14:17:22Z] Incoming HTTP/2.0 GET /api/v1/login/status request from 10.244.0.1:56140: {} 2019/08/14 14:17:22 [2019-08-14T14:17:22Z] Outcoming response to 10.244.0.1:56140 with 200 status code 2019/08/14 14:17:22 [2019-08-14T14:17:22Z] Incoming HTTP/2.0 GET /api/v1/csrftoken/token request from 10.244.0.1:56140: {} 2019/08/14 14:17:22 [2019-08-14T14:17:22Z] Outcoming response to 10.244.0.1:56140 with 200 status code 2019/08/14 14:17:22 [2019-08-14T14:17:22Z] Incoming HTTP/2.0 POST /api/v1/token/refresh request from 10.244.0.1:56140: { contents hidden } 2019/08/14 14:17:22 [2019-08-14T14:17:22Z] Outcoming response to 10.244.0.1:56140 with 200 status code 2019/08/14 14:17:22 [2019-08-14T14:17:22Z] Incoming HTTP/2.0 GET /api/v1/settings/global/cani request from 10.244.0.1:56140: {} 2019/08/14 14:17:22 [2019-08-14T14:17:22Z] Outcoming response to 10.244.0.1:56140 with 200 status code 2019/08/14 14:17:22 [2019-08-14T14:17:22Z] Incoming HTTP/2.0 GET /api/v1/settings/global request from 10.244.0.1:56140: {} 2019/08/14 14:17:22 Cannot find settings config map: configmaps "kubernetes-dashboard-settings" not found再一次是pod记录
[root@pp-tmp-test20 ~]# kubectl logs kubernetes-dashboard-5698d5bc9-ql6q8 -n kube-system Error from server: Get https://172.31.68.220:10250/containerLogs/kube-system/kubernetes-dashboard-5698d5bc9-ql6q8/kubernetes-dashboard: Forbidden我做错了什么?你能告诉我一些调查方法吗?
What I'm doing wrong ? Could you please tell me some investigating way ?
我使用的服务帐户
# cat dashboard-adminuser.yaml apiVersion: v1 kind: ServiceAccount metadata: name: admin-user namespace: kube-system # cat dashboard-adminuser-ClusterRoleBinding.yaml apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: admin-user roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: cluster-admin subjects: - kind: ServiceAccount name: admin-user namespace: kube-system推荐答案
服务帐户kubernetes-dashboard似乎无法访问所有kubernetes资源，因为它绑定到kubernetes-dashboard-minimal角色.如果将服务帐户绑定到cluster-admin角色，则不会出现此类问题.下面的YAML文件可用于实现此目的.
It seems that the serviceaccount kubernetes-dashboard doesn't have access to all kubernetes resources because it was bound to kubernetes-dashboard-minimal role. If you bind the service account to cluster-admin role , you won't get such issues. Below YAML file can be used to achieve this.
apiVersion: rbac.authorization.k8s.io/v1beta1 kind: ClusterRoleBinding metadata: name: kubernetes-dashboard labels: k8s-app: kubernetes-dashboard roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: cluster-admin subjects: - kind: ServiceAccount name: kubernetes-dashboard namespace: kube-system这篇关于kubernetes仪表板错误:“度量标准客户端运行状况检查失败:服务器找不到请求的资源(获取服务heapster)."的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
