-
Notifications
You must be signed in to change notification settings - Fork 386
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.
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
craned cpu utilization continues at 100% and resource and replicas recommended values are older #898
Labels
kind/bug
Something isn't working
Comments
Cloudzp
pushed a commit
to Cloudzp/crane
that referenced
this issue
Apr 7, 2024
Cloudzp
added a commit
to Cloudzp/crane
that referenced
this issue
Apr 7, 2024
Cloudzp
added a commit
to Cloudzp/crane
that referenced
this issue
Apr 16, 2024
Cloudzp
added a commit
to Cloudzp/crane
that referenced
this issue
Aug 20, 2024
(cherry picked from commit c48a90b)
Cloudzp
added a commit
to Cloudzp/crane
that referenced
this issue
Aug 21, 2024
(cherry picked from commit c48a90b)
Cloudzp
added a commit
to Cloudzp/crane
that referenced
this issue
Aug 21, 2024
(cherry picked from commit c48a90b)
Cloudzp
added a commit
to Cloudzp/crane
that referenced
this issue
Aug 22, 2024
(cherry picked from commit c48a90b)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using craned for Resource and Replicas recommendation in a larger cluster, when the number of workloads reaches 2w+, the CPU utilization continues to be 100% (limit 8c), resource and replicas recommended values are older( runInterval: 24h0m0s)
Reproduce steps
Expected behavior
The Resource and Replicas recommendation work properly
Screenshots
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: