Hi Marko,
Ravi Kapoor

I’ve just tried it again. I already had minikube running, but without the custom metrics option enabled, so I performed these steps:

Then I opened in my browser, found container k8s_nodejs.d15f94b5_kubia-3773182134…, clicked on it and scrolled to the bottom, where the QPS metric chart was shown (its value was zero).

Make sure Custom Metrics are actually enabled - like this:

$ minikube ssh ps aux | grep EnableCustomMetrics
root 3205 7.6 12.7 11178944 261960 ? Ssl 19:44 1:12 /usr/local/bin/localkube --extra-config=kubelet.EnableCustomMetrics=true --generate-certs=false --logtostderr=true --enable-dns=false --node-ip= --apiserver-name=minikubeCA

And make sure you’re looking at the right container, whose name starts with k8s_nodejs (and not the pod infra container, whose name starts with k8s_POD).

This are the versions I’m using:

$ minikube version
minikube version: v0.17.1
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.2", GitCommit:"08e099554f3c31f6e6f07b448ab3ed78d0520507", GitTreeState:"clean", BuildDate:"2017-01-12T04:57:25Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.3", GitCommit:"029c3a408176b55c30846f0faedf56aae5992e9b", GitTreeState:"clean", BuildDate:"1970-01-01T00:00:00Z", GoVersion:"go1.7.1", Compiler:"gc", Platform:"linux/amd64"}

Haven’t tried 1.6 yet. I’ll try it soon. Thanks for the info.

Show your support

Clapping shows how much you appreciated Marko Lukša’s story.