<p>I am able to run successfully a Kubernetes Job with multiple parallel worker processes, by following the example provided in &quot;Fine Parallel Processing Using a Work Queue&quot; in the official Kubernetes documentation
(<a href="https://kubernetes.io/docs/tasks/job/fine-parallel-processing-work-queue/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/job/fine-parallel-processing-work-queue/</a>)</p>
<p>For example, with <code>parallelism: 2</code> in the Job definition yaml file, I am able to complete the task on 2 worker pods in parallel.</p>
<p>Hence, the command:</p>
<pre><code>kubectl get jobs
</code></pre>
<p>returns:</p>
<pre><code>NAME                             COMPLETIONS   DURATION   AGE
worker                           2/1 of 2      1h         6h
</code></pre>
<p>My question is: how to interpret precisely the notation <code>2/1 of 2</code> in the completions column?
(especially what is the meaning of the <code>/1</code> part?). I cannot find anything helpful in the official documention about this.</p>
<p>Thank you for your assistance.</p>
<p>[Update] The status of the pods, when the job is completed, is the following:</p>
<pre><code>kubectl get pods
</code></pre>
<p>returns:</p>
<pre><code>NAME                                   READY   STATUS      RESTARTS   AGE
worker-dt2ss                           0/1     Completed   0          6h
worker-qm56f                           0/1     Completed   0          6h
</code></pre>

nicolas.f.g
<p>A Job that is completed when a certain number of Pods terminate successfully. The <strong>Completions</strong> specifies how many Pods should terminate successfully before the Job is completed.</p>
<p><strong>COMPLETIONS</strong> indicates the total number of pods in the job / the number of completed pods in the job. <strong>From your use case</strong> <strong>2/1</strong> indicates that there are <strong>two</strong> pods in the job in which <strong>one</strong> of the pods has been completed.</p>
<p>The <strong>DURATION</strong> indicates how long the business in the job has been running. This is useful for performance optimization.</p>
<p>And <strong>AGE</strong> is obtained by subtracting the creation time of a pod from the current time. This parameter specifies the time elapsed since the pod was created.</p>
