-
Notifications
You must be signed in to change notification settings - Fork 331
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
[question] resource reservation does not consider scale up via cluster-autoscaler #2113
Comments
@lukasmrtvy Hi, the reservation would not trigger the scale-up while the vanilla version of the cluster autoscaler is not aware of the reservation's scheduling result. For this purpose, we need to develop the CA to cooperate with the current version of the reservation. It is a good point for us to support cluster overprovision with the vanilla CA. |
Kueue has implemented https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/proposals/provisioning-request.md, could it be perhaps similar for Koordinator ? |
@lukasmrtvy Yes, they are similar in reserving resources for owner pods. I appreciate your reminder. We are interested in this protocol and maybe we can resolve the above problem with this. |
@saintube Thanks. The lack of support for CA is the main problem preventing me from adopting Koordinator, so if it is going to be implemented anytime soon, then it would be superb. |
Kindly to ask if there is somebody working for this issue? If not, I'm glad to undertake it. @saintube |
any update here? |
Hi, I don't understand correctly the reservation concept. There is an alternative mentioned in docs ( https://koordinator.sh/docs/designs/resource-reservation ) with balloon/pause pods, but these are triggering the scale-up event, thus it's possible to overprovision the cluster. Reservation does not work like this. I would like to have additional reservation for ad-hoc pods ( lets say to have two "spare" nodes to cover some peaks ). Is it possible? Thanks
The text was updated successfully, but these errors were encountered: