-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Adding delay after new nodes are provisioned by cluster-autoscaler #6707
Comments
@acesir , This is interesting and did you try adding a delay in CA scan interval https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#how-can-i-modify-cluster-autoscaler-reaction-time? |
Scan interval doesn't solve the issue as it would then slow down the time of everything being provisioned and we have mixes of GPU/CPU. The issue at hand being handled after adding nodes would minimize the effect by targeting only recently added nodes/nodepools over scan interval which would impact everything in the cluster |
As I understood I have the similar issue. |
/area cluster-autoscaler |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Which component are you using?:
cluster-autoscaler
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
When using NVIDIA GPU Operator it takes a few minutes for all the daemonsets to install required bits, like CUDA toolkit/etc before the node is advertised with GPU's to kubernetes. What ends up happening is that 2 nodes end up being provisioned due to the delay when GPU operator starts it's process and autoscaler will start adding an additional node.
Describe the solution you'd like.:
Ability to have a delay option after add would help solve this as the autoscaler would ignore adding additional nodes while GPU Operator finishes it's process and the pod is scheduled
I am not sure if there are other ways to solve this but currently we just overprovision and those nodes will scale down correctly but it can get out of hand when multiple pods are scheduled and it gets out of hand.
Here is a detailed example of how this was done in OpenShift and illustrating the same problem with GPU Operator and over provisioning: https://www.redhat.com/en/blog/autoscaling-nvidia-gpus-on-red-hat-openshift
The text was updated successfully, but these errors were encountered: