Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

cluster operator slamming API server (after NDM filtering) #1842

Closed
jefflill opened this issue Aug 13, 2023 · 1 comment
Closed

cluster operator slamming API server (after NDM filtering) #1842

jefflill opened this issue Aug 13, 2023 · 1 comment
Assignees
@marcusbooyah

Comments

@jefflill
Copy link
Collaborator

I rebuilt the node/desktop images yesterday and deployed and restarted a tiny Hyper-V cluster to verify the NDM filter list fix (where commas in Helm values need to be escaped). I watched the pods and CPU stabilize (on my Windows Home workstation) after the restart with the CPU ending up at maybe 4-8% (out of 12 vcpus).

I let this run over night and found the the cluster CPU running at 22%. It looks like the cluster operator is slamming the API server:

Image
@jefflill
Copy link
Collaborator Author

CLOSING: It looks like this is actually being caused by **CertManager/ACME: #1847

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marcusbooyah marcusbooyah

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jefflill @marcusbooyah