Skip to content
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.

Sign up for GitHub

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

Jump to bottom

introduce: rolloutStrategy #563

Merged
merged 3 commits into from
Nov 1, 2021
Merged

introduce: rolloutStrategy #563

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2812535
introduce: rolloutStrategy
etamarw Oct 30, 2021
cec5a9d
Update content/docs/2.5/concepts/scaling-jobs.md
etamarw Nov 1, 2021
980c6ed
move rolloutStartegy description & add exmaple to the base yaml
etamarw Nov 1, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions content/docs/2.5/concepts/scaling-jobs.md
View file
Open in desktop
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