Create Job¶

This page introduces how to create a job through image image and YAML file.

Job is suitable for performing one-time jobs. A Job creates one or more Pods, and the Job keeps retrying to run Pods until a certain number of Pods are successfully terminated. A Job ends when the specified number of Pods are successfully terminated. When a Job is deleted, all Pods created by the Job will be cleared. When a Job is paused, all active Pods in the Job are deleted until the Job is resumed. For more information about jobs, refer to Job.

Prerequisites¶

• In the Container Management module Access Kubernetes Cluster or Create Kubernetes Cluster, and can access the cluster UI interface.

• Create a namespace and a user.

• The current operating user should have NS Edit or higher permissions, for details, refer to Namespace Authorization.

• When there are multiple containers in a single instance, please make sure that the ports used by the containers do not conflict, otherwise the deployment will fail.

Create by image¶

Refer to the following steps to create a job using an image.

1. Click Clusters on the left navigation bar, and then click the name of the target cluster to enter the cluster details page.

   

2. On the cluster details page, click Workloads -> Jobs in the left navigation bar, and then click the Create by Image button in the upper right corner of the page.

   

3. Fill in Basic Information, Container Settings and Advanced Settings in turn, click OK in the lower right corner of the page to complete the creation.

   The system will automatically return to the job list. Click ︙ on the right side of the list to perform operations such as updating, deleting, and restarting the job.

   ![Config]](../images/job07.png)

Basic information¶

On the Create Jobs page, enter the basic information according to the table below, and click Next .

• Payload Name: Can contain up to 63 characters, can only contain lowercase letters, numbers, and a separator ("-"), and must start and end with a lowercase letter or number. The name of the same type of workload in the same namespace cannot be repeated, and the name of the workload cannot be changed after the workload is created.
• Namespace: Select which namespace to deploy the newly created job in, and the default namespace is used by default. If you can't find the desired namespace, you can go to Create a new namespace according to the prompt on the page.
• Number of Instances: Enter the number of Pod instances for the workload. By default, 1 Pod instance is created.
• Description: Enter the description information of the workload and customize the content. The number of characters should not exceed 512.

Container settings¶

Container setting is divided into six parts: basic information, life cycle, health check, environment variables, data storage, and security settings. Click the corresponding tab below to view the setting requirements of each part.

Container settings is only configured for a single container. To add multiple containers to a pod, click + on the right to add multiple containers.

Advanced settings¶

Advanced setting includes job settings, labels and annotations.

Create from YAML¶

In addition to image, creation jobs can also be created more quickly through YAML files.

1. Click Clusters on the left navigation bar, and then click the name of the target cluster to enter the cluster details page.

   

2. On the cluster details page, click Workloads -> Jobs in the left navigation bar, and then click the Create from YAML button in the upper right corner of the page.

   

3. Enter or paste the YAML file prepared in advance, click OK to complete the creation.

   

kind: Job
apiVersion: batch/v1
metadata:
  name: demo
  namespace: default
  uid: a9708239-0358-4aa1-87d3-a092c080836e
  resourceVersion: '92751876'
  generation: 1
  creationTimestamp: '2022-12-26T10:52:22Z'
  labels:
    app: demo
    controller-uid: a9708239-0358-4aa1-87d3-a092c080836e
    job-name: demo
  annotations:
    revisions: >-
      {"1":{"status":"running","uid":"a9708239-0358-4aa1-87d3-a092c080836e","start-time":"2022-12-26T10:52:22Z","completion-time":"0001-01-01T00:00:00Z"}}
spec:
  parallelism: 1
  backoffLimit: 6
  selector:
    matchLabels:
      controller-uid: a9708239-0358-4aa1-87d3-a092c080836e
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: demo
        controller-uid: a9708239-0358-4aa1-87d3-a092c080836e
        job-name: demo
    spec:
      containers:
        - name: container-4
          image: nginx
          resources:
            limits:
              cpu: 250m
              memory: 512Mi
            requests:
              cpu: 250m
              memory: 512Mi
          lifecycle: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: IfNotPresent
          securityContext:
            privileged: false
      restartPolicy: Never
      terminationGracePeriodSeconds: 30
      dnsPolicy: ClusterFirst
      securityContext: {}
      schedulerName: default-scheduler
  completionMode: NonIndexed
  suspend: false
status:
  startTime: '2022-12-26T10:52:22Z'
  active: 1

Comments