Create a Job

Console

1. Log on to the ACK console. In the left navigation pane, click Clusters.

2. On the Clusters page, click the name of your cluster. In the left navigation pane, click Workloads > Jobs.

3. On the Jobs page, click Create from Image.

4. In the Basic Information step, set the basic information for the application. Then, click Next to continue to the Container step.

5. In the General section, enter registry.cn-hangzhou.aliyuncs.com/acs-sample/nginx:latest in the Image Name field. In the Lifecycle section, enter /bin/sh in the Start > Command field and ["-c", "echo 'starting...'; COUNTER=0; while [ $COUNTER -lt 5 ]; do sleep 2; COUNTER=$((COUNTER+1)); echo $COUNTER; done; echo 'finished'; exit 0"] in the Parameter field. Then, click Next to continue to the Advanced Settings step.

   Important

   Before you pull the registry.cn-hangzhou.aliyuncs.com/acs-sample/nginx:latest image, you must enable public network access for your cluster. If you accepted the default Configure SNAT for VPC setting when you created the cluster, public network access is already enabled. If not, see Enable public network access for a cluster.

6. In the Advanced Settings step, you can configure the Job's completions and parallelism settings. Set Completions to 2. For more information about these settings, see Job overview. Then, click Launch at the bottom of the page.

   Category	Parameter	Description
   Job Settings	Completions	spec.completions: specifies the number of pods that must run to completion.
   	Parallelism	spec.parallelism: specifies the number of pods that can run in parallel.
   	Timeout	spec.activeDeadlineSeconds: Specifies the maximum runtime for the Job. If the runtime exceeds this value, the Job stops immediately, regardless of whether it is complete. This is useful for time-sensitive tasks or tasks that might get stuck in an infinite loop. The default value is 600 seconds.
   	Max. Retries	spec.backoffLimit: Specifies the maximum number of retries for failed pods. This is the total number of failures across all pods in the Job before it is marked as failed. The default value is 6.
   	Restart	template.spec.restartPolicy: Specifies the restart policy for pods after a failure. Never: If a container in the pod fails, the kubelet does not restart it. The pod is marked as Failed, and the Job controller may create a new pod, subject to the spec.backoffLimit. On Failure: If a pod fails, a new pod is created to replace it.
   Labels and Annotations	Pod labels	Add a label to each pod that belongs to the workload. Resources in the cluster, such as workloads and Services, use labels to select pods. By default, ACK adds a label in the format app:(application-name) to each pod.
   	Pod Annotations	Add an annotation to each pod that belongs to the workload. Some ACK features use annotations. You can edit the annotations when you use these features.

7. After the Job is created, you can view the Job logs in the console and see that two pods have the same output.

   The log output is: starting... 1 2 3 4 5 finished.

kubectl

1. Copy the following YAML content and save it to a file named job.yaml.

   apiVersion: batch/v1
   kind: Job
   metadata:
     name: example-job
   spec:
     completions: 2 # The Job stops after two pods complete successfully.
     parallelism: 1 # Run only one pod at a time.
     template:
       spec:
         containers:
         - name: counter
           image: registry.cn-hangzhou.aliyuncs.com/acs-sample/nginx:latest
           command: 
           - /bin/sh
           - -c
           - |
             echo "starting...";
             COUNTER=0;
             while [ $COUNTER -lt 5 ]; do
               sleep 2;
               COUNTER=$((COUNTER+1));
               echo "${COUNTER}";
             done;
             echo "finished";
             exit 0
         restartPolicy: Never # Do not restart the pod. The Job controller creates a new pod on failure.

2. Run the following command to create the Job.

   kubectl apply -f job.yaml

   Expected output:

   job.batch/example-job created

3. Wait about 15 seconds and then run the following command to check the Job status.

   kubectl get job example-job

   The following output indicates that one pod has completed and the Job is still Running.

   NAME          STATUS    COMPLETIONS   DURATION   AGE
   example-job   Running   1/2           16s        16s

4. About 40 seconds after the Job is created, run the following command to check the Job status.

   kubectl get job example-job

   The following output indicates that the Job is complete.

   NAME          STATUS     COMPLETIONS   DURATION   AGE
   example-job   Complete   2/2           27s        37s

5. Run the following command to view the Job logs.

   kubectl logs -l job-name=example-job

   Expected output:

   starting...
   1
   2
   3
   4
   5
   finished
   starting...
   1
   2
   3
   4
   5
   finished