kubernetes: Reopen for issue 75565 (high CPU utilization in Docker for mac desktop)
https://github.com/kubernetes/kubernetes/issues/75565
Was this issue ever resolved? It is closed but the symptom is still occurring on Docker for Mac Desktop with Kubernetes 1.19.7 built in.
What happened:
Docker for mac desktop version 3.2.2 (61853)
With kubernetes activated in docker for mac desktop and 4 CPUs setting docker shows ~ 30 % CPU utilization when not doing work with no pods running. With kubenetes activated in docker for mac desktop and 8 CPUs setting docker shows ~ 60-100% CPU utilization when not doing work with no pods running. With kubernetes not activated docker shows 7% when not doing work and no pods running.
What you expected to happen:
Kubernetes to not show high CPU utilization.
How to reproduce it (as minimally and precisely as possible):
Turn on kubernetes in docker for mac desktop
Anything else we need to know?:
Environment:
- Kubernetes version (use
kubectl version): 1.19.7 - Cloud provider or hardware configuration: Mac book Pro 16 (2020)
- OS (e.g:
cat /etc/os-release): OSX - Big Sur - Kernel (e.g.
uname -a): 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 - Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 17 (14 by maintainers)
This is just something api-machinery does to remove issues from a search for issues to triage. They do this as a group in a frequent meeting, fede’s account is often the one enacting the commands but it’s not fede personally.
Per the original report 75565 the issue appeared to be in kubernetes perhaps in an issue with polling multiple times a second.
“Idle master constantly burns CPU/disk polling itself #75565”
“Foritus commented on Mar 25, 2019 The disk load appears to be entirely caused by etcd, presumably a second-order effect from the api server chatting to it a lot?”
This can certainly not have been closed as chatty ‘by design’? At 8 CPUs allocated to Docker for Mac desktop battery life, heat, and CPU utilization are not practical.
Is is possible to work with the Docker for Mac team and utilize a new hook/switch/something that would tell etcd polling to enter a ‘mobile’ or CPU friendly mode and lesson whatever polling is being done here?
I do not currently have a linux laptop system to test this on.