Skip to content

Commit

Permalink
Fix typo in scaledjob-spec.md
Browse files Browse the repository at this point in the history
Signed-off-by: Jay Madden <[email protected]>
  • Loading branch information
Jay-Madden authored Oct 17, 2024
1 parent e735935 commit 5219e80
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/docs/2.15/reference/scaledjob-spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ The max number of pods that is created within a single polling period. If there
The optional property rollout.strategy 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. The order in which this termination happens can be configured via the rollout.propagationPolicy property. By default, the kubernetes background propagation is used. To change this behavior specify set propagationPolicy to `foreground`. For further information see [Kubernetes Documentation](https://kubernetes.io/docs/tasks/administer-cluster/use-cascading-deletion/#use-foreground-cascading-deletion).
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.
On the `gradual` rolloutStrategy, whenever a ScaledJob is being updated, KEDA will not delete existing Jobs. Only new Jobs will be created with the latest specs.


## scalingStrategy
Expand Down

0 comments on commit 5219e80

Please sign in to comment.