Skip to content

Create CronJob from Image

Follow the steps below to create a CronJob.

  1. In the left navigation bar, click Multicloud workload to enter the CronJob page, and click the Image creation button in the upper right corner.

  2. On the Create Task page, after configuring the basic information of the load, 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.
    • Multicloud namespace: Select the namespace where the newly created task will be deployed. The default namespace is used by default. If you cannot find the required namespace, you can create a new one according to the prompt on the page.
    • Deployment cluster: Provides three options to determine which clusters the workload will be deployed on.
    • Number of Instances: Enter the number of Pod instances for the workload. By default, 1 Pod instance is created.
    • Scheduling strategy: Provides three selection methods to determine how to allocate workload instances.
    • Description: Enter the description information of the workload and customize the content. The number of characters should not exceed 512.

    There are three ways to deploy a cluster:

    • Specify cluster: Specify a cluster by selecting the cluster name
    • Specified region: Specify the cluster by selecting the manufacturer, region, and availability zone
    • Specify tags: specify clusters by adding metrics
    • You can also choose to exclude clusters/set cluster taint tolerance/dynamic area selection in the advanced deployment strategy, and finally display which clusters are expected to be scheduled to at the bottom.

    Scheduling strategies are divided into three ways

    • Repeat: schedule the same number of instances in all selected clusters
    • Aggregation: schedule as few instances as possible in all selected clusters
    • Dynamic weight: according to the real-time schedulable maximum number of instances of all selected clusters, the total number of filled instances will be run in equal proportion

  3. On the Container Configuration page, configure the basic information of the container where the load resides, and optionally configure information such as life cycle and health check, and then click Next .

  4. On the CronJob Configuration page, configure concurrency policies, timing rules, task records, other configurations and other information

    • Concurrency strategy: Whether to allow multiple Job tasks to run in parallel.

      • Allow : A new CronJob can be created before the previous task is completed, and multiple tasks can be parallelized. Too many tasks may occupy cluster resources.
      • Forbid : Before the previous task is completed, a new task cannot be created. If the execution time of the new task is up and the previous task has not been completed, CronJob will ignore the execution of the new task.
      • Replace : If the execution time of the new task is up, but the previous task has not been completed, the new task will replace the previous task.

      The above rules only apply to multiple jobs created by the same CronJob. Multiple tasks created by multiple CronJobs are always allowed to run concurrently.

    • Timing rules: Set the time period for task execution based on minutes, hours, days, weeks, and months. Support custom Cron expressions with numbers and * , after inputting the expression, the meaning of the current expression will be prompted. For detailed expression syntax rules, please refer to Cron Schedule Syntax.

    • Task records: Set how many records of successful or failed tasks to keep. 0 means do not keep.

    • Timeout: When this time is exceeded, the task will be marked as failed to execute, and all Pods under the task will be deleted. When it is empty, it means that no timeout is set. The default is 360 s.

    • Number of retries: the number of times the task can be retried, the default value is 6.

    • Restart Policy: Set whether to restart the Pod when the task fails.

  5. On the Advanced Configuration page, you can configure task settings and labels and annotations.

    If you do not need to configure override policy after the creation is complete, you can directly use OK to complete the creation of the multicloud task

  6. On the Override Configuration page, after selecting the personalized container configuration, labels and annotations, click OK .

    You can add the corresponding override configmap in the list area on the left. After you add a differentiated configmap, you need to specify the corresponding cluster. The selectable range of the cluster is only the cluster selected at the beginning, and the selected cluster will use the specified differential configuration; the unspecified cluster will still use the default configuration.

Note

  • When creating a multicloud workload through mirroring, if you need to use the advanced capabilities of specifying a location and specifying a label to create, you need to ensure that the corresponding location or label has been set for the worker cluster; Adding tags needs to be added within a single cluster, and can be jumped to the corresponding cluster maintenance from the worker cluster management list.
  • When configuring the number of replicas, you need to pay attention to the corresponding scheduling strategy. Only when it is repeated, will all the configured replicas be started in multiple clusters.

Comments