You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone!
I needed to use the cron trigger to schedule a scale by time in a deployment and the end expression doesn't act as expected.
I'm setting start and end to run within 10 minutes, but only start is taken into account.
I needed to do the configuration below to solve the scale down:
cooldownPeriod and stabilizationWindowSeconds must have the same value to work properly, in my case 600 seconds.
I can change the end expression to any value.
I would like to only use the expressions Start and End for the CRON itself.
As mentioned in the documentation.
triggers:
- type: cron
metadata:
# Required
timezone: Asia/Kolkata # The acceptable values would be a value from the IANA Time Zone Database.
start: 30 * * * * # Every hour on the 30th minute
end: 45 * * * * # Every hour on the 45th minute
desiredReplicas: "10"
Actual Behavior
I'm setting start and end to run within 10 minutes, but only start is taken into account.
I needed to do the configuration below to solve the scale down:
cooldownPeriod and stabilizationWindowSeconds must have the same value to work properly, in my case 600 seconds.
I can change the end expression to any value.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
stalebot
added
the
stale
All issues that are marked as stale due to inactivity
label
Oct 13, 2021
Report
Hello everyone!
I needed to use the cron trigger to schedule a scale by time in a deployment and the end expression doesn't act as expected.
I'm setting start and end to run within 10 minutes, but only start is taken into account.
I needed to do the configuration below to solve the scale down:
cooldownPeriod and stabilizationWindowSeconds must have the same value to work properly, in my case 600 seconds.
I can change the end expression to any value.
Expected Behavior
I would like to only use the expressions Start and End for the CRON itself.
As mentioned in the documentation.
Actual Behavior
I'm setting start and end to run within 10 minutes, but only start is taken into account.
I needed to do the configuration below to solve the scale down:
cooldownPeriod and stabilizationWindowSeconds must have the same value to work properly, in my case 600 seconds.
I can change the end expression to any value.
Steps to Reproduce the Problem
If you run the code to trigger a deployment using Cron the problem will occur.
Logs from KEDA operator
No response
KEDA Version
2.3.0
Kubernetes Version
1.18
Platform
Amazon Web Services
Scaler Details
Cron
Anything else?
No response
The text was updated successfully, but these errors were encountered: