-
Notifications
You must be signed in to change notification settings - Fork 95
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
ScaledObject is not created #1030
Comments
Hello, |
Yes, this is my config for httpscaledobject:
And this is logs for external scaler:
Logs of keda operator:
|
I need the logs of the add-on operator (HTTP Add-on operator), not KEDA operator logs (there are 2 operators, KEDA's one and the Add-on one). scalingMetric: # requestRate and concurrency are mutually exclusive
requestRate:
granularity: 1s
targetValue: 100
window: 1m
concurrency:
targetValue: 100 |
Thank you very much, I didn't had a close look at that part that it should be only one either requestRate or concurrency. One question just, I want to scale based on request count so every time when there is request I want to trigger pod scale up, will this configuration work at that way?
|
If you don't have a continuous amount of traffic (> 1-2krmp), I'd use requestRate: scalingMetric:
requestRate:
granularity: 1s
targetValue: 100 # 100 request per second
window: 1m |
When I have changed from this:
to this:
It didn't created new ScaledObject, is that expected? |
The ScaledObject doesn't change due to this change because in v0.8.0 we introduced a change in how both items are connected, instead of updating the ScaledObject with more new info, we just reference the HTTPScaledObject in the ScaledObject (if you check the metadata section, the only fields are the external scaler address and the HTTPScaledObject name). All the changes are applied on the add-on components side (but you should still have the ScaledObject created before) |
Got it, thank you very much |
Report
Hi team, I am trying to use this to automatically scale my workloads when there is request coming to pod. I have configured 0.8.0 version of Keda http add-on.
Expected Behavior
Scale when there are requests. ScaledObject should've created.
Actual Behavior
Nothing happening, ScaledObject not created
Steps to Reproduce the Problem
Logs from KEDA HTTP operator
there isn't any valid interceptor endpoint
HTTP Add-on Version
0.8.0
Kubernetes Version
1.29
Platform
Google Cloud
Anything else?
No response
The text was updated successfully, but these errors were encountered: