我目前正在使用 Kubeadm 在裸机设置上设置 Kubernetes。集群中的每台机器都运行 Ubuntu 16.04、Kubernetes 1.9 stable、CoreDNS 和 WeaveNet。
但是，当我尝试将 Heapster 连接到 Kubernetes 仪表板时 - 没有传递任何指标。Kubernetes Dashboard 和 Heapster 的日志如下所示。我发现的所有其他人似乎都只是有查找错误，但我已经确认我的 DNS 正在使用容器中的 nslookup 工作。此外，我的日志显示对 Heapster 的初始请求已得到确认。
我的日志中是否有任何突出显示我的设置不正确的地方？
赫普斯特日志：
I0220 12:44:19.631122 1 heapster.go:72] /heapster --source=kubernetes:https://kubernetes.default --sink=influxdb:http://monitoring-influxdb.kube-system.svc:8086
I0220 12:44:19.631162 1 heapster.go:73] Heapster version v1.4.2
I0220 12:44:19.631388 1 configs.go:61] Using Kubernetes client with master "https://kubernetes.default" and version v1
I0220 12:44:19.631409 1 configs.go:62] Using kubelet port 10255
I0220 12:44:19.654779 1 influxdb.go:278] created influxdb sink with options: host:monitoring-influxdb.kube-system.svc:8086 user:root db:k8s
I0220 12:44:19.654802 1 heapster.go:196] Starting with InfluxDB Sink
I0220 12:44:19.654811 1 heapster.go:196] Starting with Metric Sink
I0220 12:44:19.667781 1 heapster.go:106] Starting heapster on port 8082
I0220 12:45:05.120667 1 influxdb.go:241] Created database "k8s" on influxDB server at "monitoring-influxdb.kube-system.svc:8086"
Kubernetes 仪表板日志：
2018/02/20 12:45:51 Starting overwatch
2018/02/20 12:45:51 Using in-cluster config to connect to apiserver
2018/02/20 12:45:51 Using service account token for csrf signing
2018/02/20 12:45:51 No request provided. Skipping authorization
2018/02/20 12:45:51 Successful initial request to the apiserver, version: v1.9.3
2018/02/20 12:45:51 Generating JWE encryption key
2018/02/20 12:45:51 New synchronizer has been registered: kubernetes-dashboard-key-holder-kube-system. Starting
2018/02/20 12:45:51 Starting secret synchronizer for kubernetes-dashboard-key-holder in namespace kube-system
2018/02/20 12:45:51 Storing encryption key in a secret
2018/02/20 12:45:51 Creating in-cluster Heapster client
2018/02/20 12:45:51 Successful request to heapster
2018/02/20 12:45:51 Auto-generating certificates
2018/02/20 12:45:51 Successfully created certificates
2018/02/20 12:45:51 Serving securely on HTTPS port: 8443
2018/02/20 12:47:08 Getting application global configuration
2018/02/20 12:47:08 Application configuration {"serverTime":1519130828354}
2018/02/20 12:47:09 [2018-02-20T12:47:09Z] Incoming HTTP/2.0 GET /api/v1/settings/global request from 10.40.0.0:57054: {}
2018/02/20 12:47:09 MSG_TOKEN_EXPIRED_ERROR
2018/02/20 12:47:09 [2018-02-20T12:47:09Z] Outcoming response to 10.40.0.0:57054 with 500 status code
2018/02/20 12:47:10 [2018-02-20T12:47:10Z] Incoming HTTP/2.0 GET /api/v1/login/status request from 10.40.0.0:57054: {}
2018/02/20 12:47:10 [2018-02-20T12:47:10Z] Outcoming response to 10.40.0.0:57054 with 200 status code
2018/02/20 12:47:10 [2018-02-20T12:47:10Z] Incoming HTTP/2.0 GET /api/v1/systembanner request from 10.40.0.0:57054: {}
2018/02/20 12:47:10 [2018-02-20T12:47:10Z] Outcoming response to 10.40.0.0:57054 with 200 status code
2018/02/20 12:47:10 [2018-02-20T12:47:10Z] Incoming HTTP/2.0 GET /api/v1/login/status request from 10.40.0.0:57054: {}
2018/02/20 12:47:10 [2018-02-20T12:47:10Z] Outcoming response to 10.40.0.0:57054 with 200 status code
2018/02/20 12:47:10 [2018-02-20T12:47:10Z] Incoming HTTP/2.0 GET /api/v1/rbac/status request from 10.40.0.0:57054: {}
2018/02/20 12:47:10 MSG_TOKEN_EXPIRED_ERROR
2018/02/20 12:47:10 [2018-02-20T12:47:10Z] Outcoming response to 10.40.0.0:57054 with 500 status code
2018/02/20 12:47:10 [2018-02-20T12:47:10Z] Incoming HTTP/2.0 GET /api/v1/csrftoken/token request from 10.40.0.0:57054: {}
2018/02/20 12:47:10 [2018-02-20T12:47:10Z] Outcoming response to 10.40.0.0:57054 with 200 status code
2018/02/20 12:47:11 [2018-02-20T12:47:11Z] Incoming HTTP/2.0 POST /api/v1/token/refresh request from 10.40.0.0:57054: {}
2018/02/20 12:47:11 [2018-02-20T12:47:11Z] Outcoming response to 10.40.0.0:57054 with 500 status code
2018/02/20 12:47:11 [2018-02-20T12:47:11Z] Incoming HTTP/2.0 GET /api/v1/node?filterBy=&itemsPerPage=10&name=&namespace=&page=1&sortBy=d,creationTimes\
tamp request from 10.40.0.0:57054: {}
2018/02/20 12:47:11 MSG_TOKEN_EXPIRED_ERROR
2018/02/20 12:47:11 [2018-02-20T12:47:11Z] Outcoming response to 10.40.0.0:57054 with 500 status code
2018/02/20 12:47:11 [2018-02-20T12:47:11Z] Incoming HTTP/2.0 GET /api/v1/login/modes request from 10.40.0.0:57054: {}
2018/02/20 12:47:11 [2018-02-20T12:47:11Z] Outcoming response to 10.40.0.0:57054 with 200 status code
2018/02/20 12:48:00 [2018-02-20T12:48:00Z] Incoming HTTP/2.0 GET /api/v1/csrftoken/login request from 10.40.0.0:57054: {}
2018/02/20 12:48:00 [2018-02-20T12:48:00Z] Outcoming response to 10.40.0.0:57054 with 200 status code
2018/02/20 12:48:00 [2018-02-20T12:48:00Z] Incoming HTTP/2.0 POST /api/v1/login request from 10.40.0.0:57054: {}
2018/02/20 12:48:00 [2018-02-20T12:48:00Z] Incoming HTTP/2.0 GET /api/v1/overview?filterBy=&itemsPerPage=10&name=&page=1&sortBy=d,creationTimestamp re\
quest from 10.40.0.0:57054: {}
2018/02/20 12:48:00 Getting config category
2018/02/20 12:48:00 Getting discovery and load balancing category
2018/02/20 12:48:00 Getting lists of all workloads
2018/02/20 12:48:00 No metric client provided. Skipping metrics.
2018/02/20 12:48:00 No metric client provided. Skipping metrics.
2018/02/20 12:48:00 No metric client provided. Skipping metrics.
2018/02/20 12:48:00 No metric client provided. Skipping metrics.
2018/02/20 12:48:00 No metric client provided. Skipping metrics.
2018/02/20 12:48:00 No metric client provided. Skipping metrics.
2018/02/20 12:48:00 No metric client provided. Skipping metrics.
2018/02/20 12:48:00 Getting pod metrics