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
Copy file name to clipboardExpand all lines: content/en/docs/concepts/workloads/controllers/cron-jobs.md
+10-5
Original file line number
Diff line number
Diff line change
@@ -161,12 +161,17 @@ When `.spec.suspend` changes from `true` to `false` on an existing CronJob witho
161
161
162
162
### Jobs history limits
163
163
164
-
The `.spec.successfulJobsHistoryLimit` and `.spec.failedJobsHistoryLimit` fields are optional.
165
-
These fields specify how many completed and failed Jobs should be kept.
166
-
By default, they are set to 3 and 1 respectively. Setting a limit to `0` corresponds to keeping
167
-
none of the corresponding kind of Jobs after they finish.
164
+
The `.spec.successfulJobsHistoryLimit` and `.spec.failedJobsHistoryLimit` fields specify
165
+
how many completed and failed Jobs should be kept. Both fields are optional.
168
166
169
-
For another way to clean up Jobs automatically, see [Clean up finished Jobs automatically](/docs/concepts/workloads/controllers/job/#clean-up-finished-jobs-automatically).
167
+
*`.spec.successfulJobsHistoryLimit`: This field specifies the number of successful finished
168
+
jobs to keep. The default value is `3`. Setting this field to `0` will not keep any successful jobs.
169
+
170
+
*`.spec.failedJobsHistoryLimit`: This field specifies the number of failed finished jobs to keep.
171
+
The default value is `1`. Setting this field to `0` will not keep any failed jobs.
172
+
173
+
For another way to clean up Jobs automatically, see
174
+
[Clean up finished Jobs automatically](/docs/concepts/workloads/controllers/job/#clean-up-finished-jobs-automatically).
0 commit comments