Skip to content

Commit

Permalink
introduce: rolloutStrategy (kedacore#563)
Browse files Browse the repository at this point in the history
Signed-off-by: etamarw <etamarw@wix.com>
Co-authored-by: Zbynek Roubalik <726523+zroubalik@users.noreply.github.com>
  • Loading branch information
etamarw and zroubalik authored Nov 1, 2021
1 parent 45bffc6 commit 5daa8bb
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions content/docs/2.5/concepts/scaling-jobs.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,7 @@ spec:
failedJobsHistoryLimit: 5 # Optional. Default: 100. How many failed jobs should be kept.
envSourceContainerName: {container-name} # Optional. Default: .spec.JobTargetRef.template.spec.containers[0]
maxReplicaCount: 100 # Optional. Default: 100
rolloutStrategy: gradual # Optional. Default: default. Which Rollout Strategy KEDA will use.
scalingStrategy:
strategy: "custom" # Optional. Default: default. Which Scaling Strategy to use.
customScalingQueueLengthDeduction: 1 # Optional. A parameter to optimize custom ScalingStrategy.
Expand Down Expand Up @@ -95,6 +96,7 @@ The actual number of jobs could exceed the limit in a short time. However, it is

This optional property specifies the name of container in the Job, from which KEDA should try to get environment properties holding secrets etc. If it is not defined it, KEDA will try to get environment properties from the first Container, ie. from `.spec.JobTargetRef.template.spec.containers[0]`.


---

```yaml
Expand All @@ -116,6 +118,18 @@ The max number of pods that is created within a single polling period. If there
* **Running Job Count:** How many jobs are running.
* **Number of the Scale:** The number of the job that is created.

---

```yaml
rolloutStrategy: default # Optional. Default: default. Which Rollout Strategy KEDA will use.
```

This optional property specifies the rollout strategy KEDA will use while updating an existing ScaledJob.
Possible values are `default` or `gradual`. \
When using the `default` rolloutStrategy, KEDA will terminate existing Jobs whenever a ScaledJob is being updated. Then, it will recreate those Jobs with the latest specs. \
On the `gradual` rolloutStartegy, whenever a ScaledJob is being updated, KEDA will not delete existing Jobs. Only new Jobs will be created with the latest specs.


---

```yaml
Expand Down

0 comments on commit 5daa8bb

Please sign in to comment.