4

After deploying anything to minikube it seems as though the apiserver starts eating up all the CPU and makes the dashboard mostly unusable until the apiserver dies and gets restarted.

I've read through a bit of the references found in this post: kube-apiserver high CPU and requests

However, those seem to specifically target deployed k8s clusters on many machines, or at least where the master isn't on the same machine.

That's not how it would work with minikube since it's a signle node cluster. Not to mention it typically isn't given a ton of resources (neither CPU or mem).

Is there a way to curb or eliminate this behavior? Perhaps I've missed some important configuration for running on minikube?

lucidquiet
  • 6,124
  • 7
  • 51
  • 88
  • How did you ensure kube-apiserver is actually the one eating CPU? – Clorichel Nov 27 '18 at 20:04
  • @Clorichel `top` %CPU at ~150%+ for kube-apiserver on local instance. – lucidquiet Nov 27 '18 at 21:34
  • How are you starting the minikube and what is being deployed? – Crou Nov 28 '18 at 11:54
  • @Crou I've seen this happen with as little as an nginx proxy container and a webserver while running filebeat getting zero traffic, of course, since it's running on a local machine. I'm only starting it with the basic `minikube start` command (nothing special). – lucidquiet Nov 28 '18 at 20:03
  • @lucidquiet have you tried starting `minikube` with more resources? – Crou Nov 29 '18 at 09:38
  • A bit late on this reply, but I have started using more resources to combat this behavior. The machine can cope once I've upped the memory to 8gb, but might work with less, I just happen to have the extra ram. – lucidquiet Aug 08 '19 at 18:48
  • Did you find a solution? I run almost empty minikube on 12 cores + 16 gb ram and kube-apiserver happily eats seven CPUs on idle configuration – Boris Treukhov Jan 24 '20 at 23:35
  • 1
    The solution appears to be run with more than the defaults and update to newer minikube if possible. – lucidquiet Jan 27 '20 at 18:14

0 Answers0