I am currently setting up Kubernetes on a bare-metal setup using Kubeadm. Each machine in the cluster is running Ubuntu 16.04 with Kubernetes 1.9 stable, CoreDNS, and WeaveNet.

However, when I attempt to connect Heapster to the Kubernetes Dashboard - no metrics are passed through. The logs of Kubernetes Dashboard and Heapster are shown below. Every other person I have found with this issue seems to simply have lookup errors, but I have confirmed that my DNS is working using nslookup from a container. Additionally, my logs show that the initial request to Heapster is confirmed.

Does anything standout in my logs as showing something incorrect in my setup?

Heapster Logs:

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 Dashboard Logs:

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