dashboard: Heapster does not work any more out of the box
If I am running 1.6.2 the logs give me the output:
[restful] 2017/07/25 15:49:13 log.go:26: No metric client provided. Skipping metrics.
[restful] 2017/07/25 15:49:13 log.go:26: No metric client provided. Skipping metrics.
And no metrics will be shown on the dashboard pages. I am using K8S 1.7.1 with the following heapster image config:
gcr.io/google_containers/heapster-grafana-amd64:v4.4.1
gcr.io/google_containers/heapster-amd64:v1.4.0
gcr.io/google_containers/heapster-influxdb-amd64:v1.1.1
Is there any configuration missing within the yml file here?
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 30 (13 by maintainers)
surely this is all to do with https://github.com/kubernetes/dashboard/issues/2306 so due to this change in heapster, right now, if you create your dashboard pod right after you create your heapster pod, the dashboard will not load the metrics client because not enough time has passed in order for heapster to gather some data … wait 5 minutes or so and restart the dashboard, it will then get the right value back from the heapster health check and metrics/graphs will suddenly start working in the dashboard… but this is far from optimal. how about removing that health check until you figure out a scheme that works reliably?
@floreks I tried this 15 minutes ago with Kubernetes 1.7.4 and Dashboard 1.6.3 and it didn’t work without that flag.
I’m currently working on adding periodic check so dashboard will try to discover heapster for around 10 min after start. In case they are deployed together it will be more than enough to automatically enable metrics once heapster scrapes some data.
restarting dashboard after 5 mins worked in my case: minikube 0.22 dashboard 1.6.3 heapster 1.3.0
That’s what you’re looking at.
Take a look at #2181. You can use these changes to make it work for now. It will be pretty much the same as in-cluster config.
Sent from my Google Nexus 5X using FastHub