-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #80901 from openshift-cherrypick-robot/cherry-pick…
…-80708-to-enterprise-4.17 [enterprise-4.17] OSDOCS:11739 add support for cron scaler in CMA
- Loading branch information
Showing
2 changed files
with
49 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
// Module included in the following assemblies: | ||
// | ||
// * nodes/cma/nodes-cma-autoscaling-custom-trigger.adoc | ||
|
||
:_mod-docs-content-type: PROCEDURE | ||
[id="nodes-cma-autoscaling-custom-trigger-cron_{context}"] | ||
= Understanding the cron trigger | ||
|
||
You can scale pods based on a time range. | ||
|
||
When the time range starts, the custom metrics autoscaler scales the pods associated with an object from the configured minimum number of pods to the specified number of desired pods. At the end of the time range, the pods are scaled back to the configured minimum. The time period must be configured in link:https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#writing-a-cronjob-spec[cron format]. | ||
|
||
[NOTE] | ||
==== | ||
The custom metrics autoscaler with cron trigger scales pods based only on the specified times and cannot scale pods on a daily, weekly, monthly, or yearly schedule. | ||
==== | ||
|
||
The following example scales the pods associated with this scaled object from `0` to `100` from 6:00 AM to 6:30 PM India Standard Time. | ||
|
||
.Example scaled object with a cron trigger | ||
[source,yaml] | ||
---- | ||
apiVersion: keda.sh/v1alpha1 | ||
kind: ScaledObject | ||
metadata: | ||
name: cron-scaledobject | ||
namespace: default | ||
spec: | ||
scaleTargetRef: | ||
name: my-deployment | ||
minReplicaCount: 0 <1> | ||
maxReplicaCount: 100 <2> | ||
cooldownPeriod: 300 | ||
triggers: | ||
- type: cron <3> | ||
metadata: | ||
timezone: Asia/Kolkata <4> | ||
start: "0 6 * * *" <5> | ||
end: "30 18 * * *" <6> | ||
desiredReplicas: "100" <7> | ||
---- | ||
<1> Specifies the minimum number of pods to scale down to at the end of the time frame. | ||
<2> Specifies the maximum number of replicas when scaling up. This value should be the same as `desiredReplicas`. The default is `100`. | ||
<3> Specifies a cron trigger. | ||
<4> Specifies the timezone for the time frame. This value must be from the link:https://data.iana.org/time-zones/tzdb-2021a/zone1970.tab[IANA Time Zone Database]. | ||
<5> Specifies the start of the time frame. | ||
<6> Specifies the end of the time frame. | ||
<7> Specifies the number of pods to scale to between the start and end of the time frame. This value should be the same as `maxReplicaCount`. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters