-
Notifications
You must be signed in to change notification settings - Fork 998
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
desiredReplicas ignored in scaledObject with trigger cron #5805
Comments
This is by design, I believe, but I still think we should kill it in favor of #3566 @kedacore/keda-maintainers |
What exactly is by design here? |
Hello @gerbil
KEDA is scaling from 0 to 1 because KEDA relies on the HPA to scaling from 1 to N, so the "usual" process is that KEDA scales from 0 to 1 when there is at least 1 active trigger, and then the HPA scales the workload from 1 to N. Given this, if you want to scale from 0 to 5 directly, it's doable. You can use
|
Working fine, thank you! |
Report
desiredReplicas
is ignored completely when using trigger cron for CRD based deploymentScaledObject:
Expected Behavior
desiredReplicas
should be respected by scaledObject cron based featureActual Behavior
ScaledObject ref always restored to
replicas: 1
ignoringdesiredReplicas
Steps to Reproduce the Problem
triggers: -metadata: desiredReplicas: '5'
Logs from KEDA operator
KEDA Version
2.14.0
Kubernetes Version
1.27
Platform
Microsoft Azure
Scaler Details
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: