whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

API Ref v1.22 alpha.3

Browse Source
This commit is contained in:
Philippe Martin
2021-06-26 11:26:10 +02:00
parent 6848d25094
commit d531f1d97b
58 changed files with 793 additions and 666 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/kubernetes-api/workload-resources/job-v1.md
+7 -3
View File
@@ -6,7 +6,7 @@ api_metadata:
content_type: "api_reference"
description: "Job represents the configuration of a single job."
title: "Job"
weight: 10
weight: 9
auto_generated: true
---
@@ -86,9 +86,9 @@ JobSpec describes how the job execution will look like.
`NonIndexed` means that the Job is considered complete when there have been .spec.completions successfully completed Pods. Each Pod completion is homologous to each other.
`Indexed` means that the Pods of a Job get an associated completion index from 0 to (.spec.completions - 1), available in the annotation batch.kubernetes.io/job-completion-index. The Job is considered complete when there is one successfully completed Pod for each index. When value is `Indexed`, .spec.completions must be specified and `.spec.parallelism` must be less than or equal to 10^5.
`Indexed` means that the Pods of a Job get an associated completion index from 0 to (.spec.completions - 1), available in the annotation batch.kubernetes.io/job-completion-index. The Job is considered complete when there is one successfully completed Pod for each index. When value is `Indexed`, .spec.completions must be specified and `.spec.parallelism` must be less than or equal to 10^5. In addition, The Pod name takes the form `$(job-name)-$(index)-$(random-string)`, the Pod hostname takes the form `$(job-name)-$(index)`.
This field is alpha-level and is only honored by servers that enable the IndexedJob feature gate. More completion modes can be added in the future. If the Job controller observes a mode that it doesn't recognize, the controller skips updates for the Job.
This field is beta-level. More completion modes can be added in the future. If the Job controller observes a mode that it doesn't recognize, the controller skips updates for the Job.
- **backoffLimit** (int32)
@@ -639,6 +639,8 @@ PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}
200 (<a href="{{< ref "../workload-resources/job-v1#Job" >}}">Job</a>): OK
201 (<a href="{{< ref "../workload-resources/job-v1#Job" >}}">Job</a>): Created
401: Unauthorized
@@ -692,6 +694,8 @@ PATCH /apis/batch/v1/namespaces/{namespace}/jobs/{name}/status
200 (<a href="{{< ref "../workload-resources/job-v1#Job" >}}">Job</a>): OK
201 (<a href="{{< ref "../workload-resources/job-v1#Job" >}}">Job</a>): Created
401: Unauthorized