Minikube: Minikube v0.23.0 100% CPU usage from kubernetes-dashboard v1.7.0

Created on 29 Oct 2017  路  4Comments  路  Source: kubernetes/minikube

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug Report (and Feature Request to pull in the fix).

Please provide the following details:

Environment:

Minikube version: v0.23.0

  • OS: Red Hat Enterprise Linux Workstation release 7.3 (Maipo)
  • VM Driver: kvm
  • ISO version: minikube-v0.23.6.iso
  • Install tools: -na-
  • Others: -na-

What happened:
Minikube VM burns 100% of a CPU

What you expected to happen:
Hopefully stay as close to idle as possible.

How to reproduce it (as minimally and precisely as possible):
Start a minikube VM with latest v0.23.0 -- run top within a minikube ssh session and note that dashboard container is burning 100% of a vCPU.

Output of minikube logs (if applicable):
-na-

Anything else do we need to know:
This is an upstream kubernetes/dashboard bug fixed at: https://github.com/kubernetes/dashboard/issues/2401
Request cutting patch release of Minikube that pulls in kubernetes/dashboard v1.7.1 -- that has the fix.

kinbug

Most helpful comment

You can also disable the dashboard addon with minikube addons disable dashboard

We have a PR open to update to 1.7.1, I'll prioritize reviewing that and getting it merged https://github.com/kubernetes/minikube/pull/2112

All 4 comments

Workaround:

$ kubectl get pods -n kube-system -o name | grep dashboard | xargs kubectl delete -n kube-system

to bounce the dashboard pod when it gets into the spin-loop 100% CPU state.

You can also disable the dashboard addon with minikube addons disable dashboard

We have a PR open to update to 1.7.1, I'll prioritize reviewing that and getting it merged https://github.com/kubernetes/minikube/pull/2112

We've merged 1.7.1 and it will be in the next release.

Excellent in the meantime i confirmed that the problem and solution for a workaround work.

Was this page helpful?
0 / 5 - 0 ratings