Scaling down logic #3551
Replies: 3 comments 3 replies
-
KEDA is building on top of the built-in HPA of Kubernetes and only provides the metrics you provide, so in the end HPA will decide what pod will be terminated which is random. I would suggest, however, to open a new issue (if none already exists) to keep track of scale down logic to determine instance to be killed (ie by calling an API). However, this will not happen soon. |
Beta Was this translation helpful? Give feedback.
-
@tomkerkhove thanks for you response. I will create separate feature request. Can you please provide
Could you at least estimate the delivery of this task - would it be a month, half a year, year or longer? That info would be very useful to redesign project roadmap, so thank you in advance! :) |
Beta Was this translation helpful? Give feedback.
-
@Tazovsky Did they implemented this feature? Can you please share feature request link for others to keep track of it? |
Beta Was this translation helpful? Give feedback.
-
I am using Keda Metrics API scaler. My API checks which pods have user logged into pods, sends info to Keda, Keda scales up if there is no free pod - in my setup each user gets pods exclusively. But when API sends metric value to scale down, then Keda may kill pods which have active user logged in.
For example, et's assume I have 5 pods:
targetValue == 1
and value returned from API is4
- Keda starts scaling down, so which pods will be terminated?I also have following questions:
Beta Was this translation helpful? Give feedback.
All reactions