We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What happened: kubelet/dockerd consume a lot of CPU on Windows node, I guess the System interrupts cpu usage is also caused by them.
I was able to get pprof cpu profile from kubelet.
aks.pb.gz
What you expected to happen: cpu usage for kubelet/dockerd are normal.
How to reproduce it (as minimally and precisely as possible): Not sure, only one of our Windows nodes encounters this issue.
Environment:
kubectl version
The text was updated successfully, but these errors were encountered:
Closing in favor of support request if still occurring.
Sorry, something went wrong.
@immuzz Can you confirm you're looking into this?
@mikkelhegn Yes we are looking into this issue.
immuzz
No branches or pull requests
What happened:
kubelet/dockerd consume a lot of CPU on Windows node, I guess the System interrupts cpu usage is also caused by them.
I was able to get pprof cpu profile from kubelet.
aks.pb.gz
What you expected to happen:
cpu usage for kubelet/dockerd are normal.
How to reproduce it (as minimally and precisely as possible):
Not sure, only one of our Windows nodes encounters this issue.
Environment:
kubectl version
): 1.14.8The text was updated successfully, but these errors were encountered: