#DOCKER HYPERKIT USING 2GB OF MEMORY ISO#

I might be wrong, but high load seems to be caused by running quite often kubectl process similar to this one. Output of minikube logs (if applicable): n/a How to reproduce it (as minimally and precisely as possible):Д¬reate a minikube cluster on macOS with the appropriate versions. But when running in minikube mode, it'd really be nice to slow down the CPU consumption so that we don't kill all of our laptop batteries. I understand that this may just be the baseline CPU usage for some of these services (liveness checks, etc). I expected the CPU usage to fall to basically zero when at rest. It looks like kube-apiserver-minikube and kube-controller-manager-minikube are the primary offenders. I ran minikube addons enable heapster to get some insight into where all the CPU is going. I've observed the same behavior across both hyperkit and VirtualBox. CPU usage is pegged at ~50% even though no pods have been launched and nothing is happening on the cluster. I just installed and set up a fresh minikube cluster.

#DOCKER HYPERKIT USING 2GB OF MEMORY ISO#

cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): v0.29.0 cat ~/.minikube/machines/minikube/config.json | grep DriverName): hyperkit Minikube version (use minikube version): v0.29.0 Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Docker hyperkit using 2gb of memory