You can configure local storage to mount the files or directories in the file system of a host to a pod.

Background information

In a Container Service Kubernetes cluster of Enterprise Distributed Application Service (EDAS), you can configure local storage by using the hostPath volume, which allows containers to store files by using the high-speed file system of the host.

Configure local storage when you create an application

  1. Log on to the EDAS console.
  2. In the left-side navigation pane, click Applications. In the top navigation bar, select a region. On the Applications page, select a namespace in the upper part and click Create Application in the upper-left corner.
  3. In the Basic Information step, specify Cluster Type and Application Runtime Environment, and click Next.
    Parameter Description
    Cluster Type Select Kubernetes Clusters.
    Application Runtime Environment Select an application runtime environment based on the type of the hosted application.
    • Java
      • Custom: Select this option if you want to use a custom image to deploy the application in a Kubernetes cluster.
      • Java: Select this option if you want to use a universal JAR package to deploy the application as a Dubbo or a Spring Boot application. You can specify the Java Environment parameter after you select this option.
      • Tomcat: Select this option if you want to use a universal WAR package to deploy the application as a Dubbo or a Spring application. You can specify the Java Environment and Container Version parameters after you select this option.
      • EDAS-Container (HSF): Select this option if you want to use a WAR or FatJar package to deploy the application as a High-Speed Service Framework (HSF) application. You can specify the Java Environment, Pandora Version, and Ali-Tomcat Version parameters after you select this option.
    • PHP: Select this option if you want to run this application as a PHP application on Apache HTTP Server.
    • Node.js, C ++, Go, and Other Languages: Select this option if you want to use a custom image to deploy the application in a Kubernetes cluster. The configuration process for multi-language applications is not described in this topic. For more information, see Use custom images to deploy applications of different programming languages in Kubernetes clusters.
  4. In the Configurations step, configure the environment information, basic information, deployment method, and resource parameters for the application, and click Next.
  5. In the Advanced Application Settings step, click Local Storage and configure local storage as needed.
    File Type Value Description
    Default value Null string Indicates that the file is directly mounted without a file type check.
    (Create) File Directory DirectoryOrCreate The file directory. If no file directory exists, a new directory is created.
    File Directory Directory The file directory. If the file directory does not exist, container startup fails.
    (Create) File FileOrCreate The file. If the file does not exist, a new file is created.
    File File The file. If the file does not exist, container startup fails.
    Socket Socket The standard UNIX Socket file. If the file does not exist, container startup fails.
    CharDevice CharDevice The character device file. If the file does not exist, container startup fails.
    BlockDevice BlockDevice The block storage device file. If the file does not exist, container startup fails.
  6. Click Create Application.
  7. In the Creation Completed step, confirm the settings in Basic Information, Configurations, and Advanced Settings, and click Create Application.
    In the upper part of the Application Overview page, click View Details. On the Change List page, you can view the change process. Wait a few minutes until the application is deployed. After the change process is complete, view the running status of the instances in the Basic Information section of the Application Overview page. If the pod that runs the application is in the running state, the application is deployed.

Configure local storage when you update an application

You can configure local storage when you create an application, or configure or update local storage when you deploy an application.

  1. Log on to the EDAS console.
  2. In the left-side navigation pane, click Applications. In the top navigation bar, select a region. On the Applications page, select a namespace in the upper part, and select Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list. Then, find the application that you want to deploy, and click the application name.
  3. On the Application Overview or Basic Information page, choose Deploy > Deploy in the upper-right corner.
  4. On the Select Deployment Mode page, select a deployment mode and click Start Deployment in the upper-right corner of the specified deployment mode section.
  5. Set the environment and deployment package for an application, click Local Storage, complete the configuration as needed, and then click OK.
    File Type Value Description
    Default value Null string Indicates that the file is directly mounted without a file type check.
    (Create) File Directory DirectoryOrCreate The file directory. If no file directory exists, a new directory is created.
    File Directory Directory The file directory. If the file directory does not exist, container startup fails.
    (Create) File FileOrCreate The file. If the file does not exist, a new file is created.
    File File The file. If the file does not exist, container startup fails.
    Socket Socket The standard UNIX Socket file. If the file does not exist, container startup fails.
    CharDevice CharDevice The character device file. If the file does not exist, container startup fails.
    BlockDevice BlockDevice The block storage device file. If the file does not exist, container startup fails.
    Notice The application is restarted after you click OK. We recommend that you perform this operation during off-peak hours.

Verify the result

  • Method 1

    In the left-side navigation pane of the application details page, click Change List to view the application change details. If the value in the Change Status column is Succeeded, the application is deployed and the configuration takes effect.

  • Method 2

    On the Application Overview page, click Running Pods (Click View) next to Running Status. In the Pod section of the panel that appears, check the Status column of the pod. If a green dot appears, the application is in the running state. This means that the application is deployed as expected and the configuration takes effect.