Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: robinvd The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
1 similar comment
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: robinvd The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
f38c91d to
2ea3c3c
Compare
Signed-off-by: Robin <robinvandijk@klippa.com>
2ea3c3c to
8e46c1c
Compare
|
Hey @robinvd, have you been using HPA based on GPU load successfully? I would love to see this being integrated. |
|
@vinismarques yes using this setup im running an autoscaling setup based on gpu load. |
Motivation
We need automatic scaling for servingruntimes based on some gpu load metric. The default deployment included metrics including prometheus. Using keda we want to scale based on prometheus queries.
The current options for scaling are
hpaannotation. But this creates a managed hpa that only works with the buildin kubernetes metrics. Adding another hpa will conflict with the already created one.This PR adds the
externaloption where the controller wont set the replicas and wont create an hpa.Modifications
The already existing External AutoscalerClass is now checked for instead of crashing the controller. The behavior is the same as
Noneexcept it does not set the replicas property.Result
potentially/partially solves #372