From 65ca8e69f28432c017d431cae3019a693851d4fa Mon Sep 17 00:00:00 2001 From: shibataka000 Date: Thu, 17 Jan 2019 20:20:28 +0900 Subject: [PATCH] Replace NO-BREAK SPACE to SPACE. (#10878) --- .../concepts/workloads/controllers/jobs-run-to-completion.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md b/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md index 8b441927fb..214fe74b41 100644 --- a/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md +++ b/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md @@ -133,8 +133,8 @@ There are three main types of jobs: - the job is complete when there is one successful pod for each value in the range 1 to `.spec.completions`. - **not implemented yet:** Each pod passed a different index in the range 1 to `.spec.completions`. 1. Parallel Jobs with a *work queue*: -  - do not specify `.spec.completions`, default to `.spec.parallelism`. -  - the pods must coordinate with themselves or an external service to determine what each should work on. + - do not specify `.spec.completions`, default to `.spec.parallelism`. + - the pods must coordinate with themselves or an external service to determine what each should work on. - each pod is independently capable of determining whether or not all its peers are done, thus the entire Job is done. - when _any_ pod terminates with success, no new pods are created. - once at least one pod has terminated with success and all pods are terminated, then the job is completed with success.