Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

kubelite process takes huge amount of CPU

See original GitHub issue

After getting the 1.21 package from Debian 10 repo, the kubelite process is eating up a lot of CPU. The process keep using >100% CPU in top and the average uptime load is ~2 instead of <1 in previous versions.

inspection-report-20210420_092101.tar.gz

Issue Analytics

State:
Created 2 years ago
Comments:41 (11 by maintainers)

Top GitHub Comments

2reactions

AmilaDevopscommented, Jul 28, 2021

hi, is any one knows after upgrading to my k8s cluster into v1.21 was this kubelite process issue have to deal with the kernel versions I’m having in my Ubuntu O/S ? Because i’m getting this cpu 100% issue only in a one node of my microk8s cluster (which has a higher kernel version when comparing with other nodes). All other nodes are fine.

tnx

2reactions

krichter722commented, Jul 6, 2021

I experienced rather high CPU consumption with a DNS forward loop as well on 1.21 after the crash loop mentioned above was no longer an issue for me. I set up calico and a IPv4+6 dual stack, but I don’t see why this might not happen with other setups as well, e.g. if your ISP provides strange DNS settings.

Therefore I needed to add --resolv-conf=/run/systemd/resolve/resolv.conf to /var/snap/microk8s/current/args/kubelet and setup the coredns configmap accordingling, see https://coredns.io/plugins/loop/ and https://microk8s.io/docs/addon-dns for a detailed explanation.

For me the issue was a huge amount of probe failures which also contributed to the high CPU usage which then probably lead to even more probe failures, but this issue might be worth taking a look at when investigating high CPU usage.