-
Notifications
You must be signed in to change notification settings - Fork 31
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
Kube-burner cleaning should go before scaling down #194
Comments
@skordas do we need to update this in other workloads other than kube-burner or can we close this issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When 120 node cluster is loaded with projects - then scaling down this cluster to 3 nodes with the same number of pods can hit cluster maximum.
My proposition is moving benchmark-cleaner before cluster-workers-scaling
The text was updated successfully, but these errors were encountered: