File tree Expand file tree Collapse file tree 1 file changed +1
-6
lines changed
content/en/docs/concepts/workloads/controllers Expand file tree Collapse file tree 1 file changed +1
-6
lines changed Original file line number Diff line number Diff line change @@ -304,7 +304,7 @@ cleaned up by CronJobs based on the specified capacity-based cleanup policy.
304
304
305
305
# ## TTL mechanism for finished Jobs
306
306
307
- {{< feature-state for_k8s_version="v1.12 " state="alpha " >}}
307
+ {{< feature-state for_k8s_version="v1.21 " state="beta " >}}
308
308
309
309
Another way to clean up finished Jobs (either `Complete` or `Failed`)
310
310
automatically is to use a TTL mechanism provided by a
@@ -342,11 +342,6 @@ If the field is set to `0`, the Job will be eligible to be automatically deleted
342
342
immediately after it finishes. If the field is unset, this Job won't be cleaned
343
343
up by the TTL controller after it finishes.
344
344
345
- Note that this TTL mechanism is alpha, with feature gate `TTLAfterFinished`. For
346
- more information, see the documentation for
347
- [TTL controller](/docs/concepts/workloads/controllers/ttlafterfinished/) for
348
- finished resources.
349
-
350
345
# # Job patterns
351
346
352
347
The Job object can be used to support reliable parallel execution of Pods. The Job object is not
You can’t perform that action at this time.
0 commit comments