Use a Job to create an application

Procedure

1. Log on to the ACK console.
2. In the left-side navigation pane, click Clusters.
3. On the Clusters page, find the cluster that you want to manage and click the name of the cluster or click Details in the Actions column. The details page of the cluster appears.
4. In the left-side navigation pane of the details page, choose Workloads > Jobs.
5. On the Jobs page, click Create from Image in the upper-right corner of the page.
   • Name: the name of the application.
   • Type: the application type. Select Jobs from the drop-down list.
     Note The application is created by using a Job in this example.
   • Label: Add a label to the application. The label is used to identify the application.
   • Annotations: Add an annotation to the application.
   • Synchronize Timezone: Specify whether to synchronize the time zone between nodes and containers.

   

6. Configure containers.
   Note You can configure one or more containers for the pods of the application.
   1. Configure basic settings.
      • Image Name: Select an image.
        • To use a Docker image or an image from Container Registry, click Select Image. In the dialog box that appears, select an image and click OK. In this example, an NGINX image is selected. On the Search tab, you can select Docker Images from the drop-down list, enter NGINX in the search box, and then click Search.
          • Alibaba Cloud Container Registry: On the Alibaba Cloud Container Registry tab, you can select an image from Container Registry. You must specify the region and Container Registry instance of the image. For more information about Container Registry, see What is Container Registry Enterprise Edition?.
            Note On the Alibaba Cloud Container Registry tab, you can search images by name in Container Registry.
          • Docker Official Images: On the Docker Official Images tab, you can select a Docker image.
          • Favorite Images: On the Favorite Images tab, you can select a Docker image that you have specified as one of your favorite images.
          • Search: On the Search tab, you can select Alibaba Cloud Images from the drop-down list and specify a region to search for an image in Container Registry. You can also select Docker Images from the drop-down list and search for a Docker image.
        • You can also enter the address of a private registry. The registry address must be in the following format: domainname/namespace/imagename:tag.
      • Image Version:
        • Click Select Image Version and select an image version. If you do not specify an image version, the latest image version is used.
        • You can select the following image pull policies:
          • ifNotPresent: If the image you want to pull is found in the region where the cluster is deployed, the local image is used. Otherwise, ACK pulls the image from the corresponding repository.
          • Always: ACK pulls the image from the repository each time the application is deployed or expanded.
          • Never: ACK uses only local images.
          Note If you select Image Pull Policy, no image pull policy is applied for the deployment of the application.
        • To pull the image without a secret, click Set Image Pull Secret to set a secret for pulling images. For more information, see Use aliyun-acr-credential-helper to pull images without a password.
      • Always: If you do not select this option, ACK caches the pulled image. This improves the efficiency of pulling and deploying images. If the specified image version is the same as the cached image version, ACK deploys the application from the cached image. Therefore, when you update the application code, if you do not change the image version for reasons such as to support the upper-layer workloads, the previously cached image is used. If you set Image Pull Policy to Always, ACK pulls the image from the repository each time the application is deployed. This ensures that the latest image and code are used.
      • Set Image Pull Secret: If you use a private image, we recommend that you configure a Secret to secure the image. For more information, see Create an application by using an image pull secret.
      • Resource Limit: You can specify an upper limit for the CPU and memory resources that the application can consume. This prevents the application from occupying an excessive amount of resources. CPU resources are measured in millicores. Each millicore is one thousandth of one core. Memory resources are measured in bytes, which can be GiB, MiB, or KiB.
      • Required Resources: The amount of CPU and memory resources that are reserved for the application. These resources are exclusive to the container. This prevents the application from becoming unavailable when other Services or processes occupy these resources.
      • Container Start Parameter: Select stdin to send the input from the ACK console to the container. Select tty to send start parameters that are defined in a virtual terminal to the console.
      • Privileged Container: If you select Privileged Container, privileged=true is set for the container. This indicates that the privilege mode is enabled. If you do not select Privileged Container, privileged=false is set for the container. This indicates that the privilege mode is disabled.
      • Init Container: If you select this check box, an init container is created. Init containers contain practical tools. For more information, see Init Container.
      • Port: Set the host port and container port. TCP and UDP are supported.

      

   2. Optional:Set parameters in the Environments section.

      You can set environment variables in key-value pairs for pods. Environment variables are used to apply pod configurations to containers. For more information, see Pod variables.

   3. Optional:Set parameters in the Health Check section.

      Health check settings include liveness and readiness probes. Liveness probes determine when to restart the container. Readiness probes indicate whether the container is ready to accept network traffic. For more information, see Health checks.

      

      Request type	Description
      HTTP	Sends an HTTP GET request to the container. You can set the following parameters: Protocol: HTTP or HTTPS. Path: the requested path on the server. Port: the container port that you want to open. Enter a port number from 1 to 65535. HTTP Header: the custom headers in the HTTP request. Duplicate headers are allowed. You can specify the HTTP headers in key-value pairs. Initial Delay (s): the initialDelaySeconds field in the YAML file. This field specifies the amount of time (in seconds) that the system must wait before it can send the first probe to a launched container. Default value: 3. Period (s): the periodSeconds field in the YAML file. This field specifies the interval (in seconds) at which probes are sent. Default value: 10. Minimum value: 1. Timeout (s): the timeoutSeconds field in the YAML file. This field specifies the timeout period (in seconds) of probes. Default value: 1. Minimum value: 1. Healthy Threshold: the minimum number of times that an unhealthy container must consecutively pass health checks before it is considered healthy. Default value: 1. Minimum value: 1. For liveness probes, this parameter must be set to 1. Unhealthy Threshold: the minimum number of times that a healthy container must consecutively fail health checks before it is considered unhealthy. Default value: 3. Minimum value: 1.
      TCP	Sends a TCP socket to the container. Kubelet attempts to open the socket on the specified port. If the connection can be established, the container is considered healthy. Otherwise, the container is considered unhealthy. Supported parameters include: Port: the container port that you want to open. Enter a port number from 1 to 65535. Initial Delay (s): the initialDelaySeconds field in the YAML file. This field specifies the amount of time (in seconds) that the system must wait before it can send the first probe to a launched container. Default value: 15. Period (s): the periodSeconds field in the YAML file. This field specifies the interval (in seconds) at which probes are sent. Default value: 10. Minimum value: 1. Timeout (s): the timeoutSeconds field in the YAML file. This field specifies the timeout period (in seconds) of probes. Default value: 1. Minimum value: 1. Healthy Threshold: the minimum number of times that an unhealthy container must consecutively pass health checks before it is considered healthy. Default value: 1. Minimum value: 1. For liveness probes, this parameter must be set to 1. Unhealthy Threshold: the minimum number of times that a healthy container must consecutively fail health checks before it is considered unhealthy. Default value: 3. Minimum value: 1.
      Command	Runs a probe command in the container to check the health status of the container. Supported parameters include: Command: the probe command that is run to check the health status of the container. Initial Delay (s): the initialDelaySeconds field in the YAML file. This field specifies the amount of time (in seconds) that the system must wait before it can send the first probe to a launched container. Default value: 5. Period (s): the periodSeconds field in the YAML file. This field specifies the interval (in seconds) at which probes are sent. Default value: 10. Minimum value: 1. Timeout (s): the timeoutSeconds field in the YAML file. This field specifies the timeout period (in seconds) of probes. Default value: 1. Minimum value: 1. Healthy Threshold: the minimum number of times that an unhealthy container must consecutively pass health checks before it is considered healthy. Default value: 1. Minimum value: 1. For liveness probes, this parameter must be set to 1. Unhealthy Threshold: the minimum number of times that a healthy container must consecutively fail health checks before it is considered unhealthy. Default value: 3. Minimum value: 1.

   4. Optional:Configure the lifecycle of the container.

      You can set the following parameters to configure the lifecycle of the container: Start, Post Start, and Pre Stop. For more information, see Configure the lifecycle of a container.

      • Start: Set the command and parameter that take effect before the container starts.
      • Post Start: Set the command that takes effect after the container starts.
      • Pre Stop: Set the command that takes effect before the container stops.

      
   5. Optional:Configure volumes.

      Local storage and cloud storage are supported.

      • Local storage: You can select HostPath, ConfigMap, Secret, and EmptyDir. The storage volume is mounted to a path in the container. For more information, see Volumes.
      • Cloud storage: supports disks, Apsara File Storage NAS (NAS) file systems, and Object Storage Service (OSS) buckets.
   6. Optional:Configure Log Service. You can specify collection configurations and custom tags.
      Note Make sure that the Log Service agent is installed in the cluster.

      You can set the Collection Configuration parameter.

      • Logstore: Create a Logstore in Log Service to store the collected log data.
      • Log Path in Container: Specify stdout or a path to collect log data.
        • stdout: specifies that the stdout files are collected.
        • Text Logs: specifies that the log files in the specified path of the container are collected. Wildcard characters can be used in the path.

      You can also add tags. Tags are added to the logs of the container when the logs are collected. Log data with tags is easier to aggregate and filter.

7. After you complete the configurations, click Next.
8. Configure advanced settings.

   You can set parameters in the Job Setting section.

   Parameter	Description
   Completions	The number of pods that the Job must run. Default value: 1.
   Parallelism	The number of pods that the Job must run in parallel at any time. Default value: 1.
   Timeout	The activeDeadlineSeconds field in the YAML file. This field specifies the operating time limit of the Job. If the Job is not complete within the time limit, the system attempts to terminate the Job.
   BackoffLimit	The backoffLimit field in the YAML file. This field specifies the number of retries that are performed by the Job upon failure. Each time the Job fails, the failed pods associated with the Job are restarted with time delay. The time delay exponentially increases until a maximum of six minutes. Default value: 6.
   Restart	Only Never and OnFailure restart policies are supported.

   

9. Click Create.
10. After the application is deployed, you are redirected to the Complete wizard page. The resource objects of the application are displayed.

    

    You can click View Details to view application details.

    You can view the status of pods in the Status column. In this example, two pods are created in parallel based on the configuration of the Job.

    Wait until all pods are created.

11. Click the Back icon in the upper-left corner of the page. On the Jobs page, you can view the time when the Job is complete.
    Note If the pods associated with the Job are not complete, the end time is not displayed.

What to do next

In the left-side navigation pane of the ACK console, click Clusters to go to the Clusters page. Find the cluster that you want to manage, and click the cluster name or click Details in the Actions column. On the details page of the cluster, choose Workloads and Jobs in the left-side navigation pane. On the Jobs page, find the application that you want to manage, and click the application name or click Details in the Actions column. On the details page of the application, you can scale and refresh the application. You can also view the YAML file of the application.

• Scale: On the details page of the application, click Scale in the upper-right corner of the page to scale the application to a required number of replicated pods.
• View the YAML file: On the details page of the application, click View in YAML in the upper-right corner of the page. You can update and download the YAML file. You can also save the YAML file as a template.
• Refresh: On the details page of the application, click Refresh in the upper-right corner of the page to update the application details.