You can mount a file directory of the host where the container is located (corresponding to hostPath in Kubernetes) or a temporary directory of the host (corresponding to emptyDir in Kubernetes) to the specified path of a container. You can also mount ConfigMaps and secrets defined in Kubernetes to the specified path of a container.

• hostPath: mounts a file directory of the host where the container is located to the specified mount point of the container. For example, if the container needs to access /etc/hosts, you can use a hostPath volume to map /etc/hosts.
• emptyDir: stores data temporarily. An emptyDir volume is first created when a pod is assigned to a node, and exists as long as that pod is running on that node. When the pod is deleted, the emptyDir volume is deleted and its data is lost.
• ConfigMap: A ConfigMap can be mounted as a volume, and all contents stored in its key are mounted onto the specified container directory. A ConfigMap is a type of resource that stores configuration data required by a workload. Its contents are user-defined. For details about how to create a ConfigMap, see Creating a ConfigMap. For details about how to use a ConfigMap, see Using a ConfigMap.
• Secret: You can store sensitive information, such as passwords, in secrets and mount them as files for use by pods. All contents in a secret are user-defined. For details about how to create a secret, see Creating a Secret. For details about how to use a secret, see Using a Secret.

The following describes how to mount these four types of volumes.

1. Create a workload by referring to Creating a Deployment, Creating a StatefulSet, or Creating a DaemonSet. When adding a container, expand Data Storage, and click Add Local Volume.
2. Set parameters for adding a local volume, as listed in Table 1.

   Table 1 Setting parameters for mounting a hostPath volume

   Parameter	Description
   Type	Select HostPath.
   Host Path	Path of the host to which the local volume is to be mounted, for example, /etc/hosts. NOTE: Host Path cannot be set to the root directory /. Otherwise, the mounting fails. Mount paths can be as follows: /opt/xxxx (excluding /opt/cloud) /mnt/xxxx (excluding /mnt/paas) /tmp/xxx /var/xxx (excluding key directories such as /var/lib, /var/script, and /var/paas) /xxxx (It cannot conflict with the system directory, such as bin, lib, home, root, boot, dev, etc, lost+found, mnt, proc, sbin, srv, tmp, var, media, opt, selinux, sys, and usr.) Do not set this parameter to /home/paas, /var/paas, /var/lib, /var/script, /mnt/paas, or /opt/cloud. Otherwise, the system or node installation will fail.
   Add Container Path	Configure the following parameters: subPath: Enter a subpath, for example, tmp. A subpath is used to mount a local disk so that the same data volume is used in a single pod. If this parameter is left blank, the root path is used by default. Container Path: Enter the path of the container, for example, /tmp. This parameter indicates the container path to which a data volume will be mounted. The container path cannot be a system directory, such as / or /var/run. Otherwise, the container may not function properly. You are advised to mount the volume to an empty directory. If the directory is not empty, ensure that there are no files affecting container startup in the directory. Otherwise, such files will be replaced, resulting in failures to start the container and create the workload. NOTICE: If the volume is mounted to a high-risk directory, you are advised to use an account with minimum permissions to start the container; otherwise, high-risk files on the host machine may be damaged. Permission Read-only: You can only read the data volumes in the path. Read/Write: You can modify the data volumes in the path. Newly written data is not migrated if the container is migrated, which may cause a data loss. Click Add Container Path to add multiple settings. Then, click OK.

1. Create a workload by referring to Creating a Deployment, Creating a StatefulSet, or Creating a DaemonSet. After you add a container, expand Data Storage, and click Add Local Volume.
2. Set the local volume type to EmptyDir and set parameters for adding a local volume, as described in Table 2.

   Table 2 Setting parameters for mounting an emptyDir volume

   Parameter	Description
   Type	Select EmptyDir.
   Medium	If you select Memory, the running speed is improved, but the storage capacity is limited by the memory size. This mode applies to scenarios where the data volume is small and the read and write efficiency is high. NOTE: If you select Memory, any files you write will count against your container's memory limit. Pay attention to the memory quota. If the memory usage exceeds the threshold, OOM may occur. If Memory is selected, the size of an emptyDir volume is 50% of the pod specifications and cannot be changed. If Memory is not selected, emptyDir volumes will not occupy the system memory. If Memory is not selected, data is stored in disks, which is applicable to a large amount of data with low requirements on read and write efficiency.
   Add Container Path	Configure the following parameters: subPath: Enter a subpath, for example, tmp. A subpath is used to mount a local disk so that the same data volume is used in a single pod. If this parameter is left blank, the root path is used by default. Container Path: Enter the path of the container, for example, /tmp. This parameter indicates the container path to which a data volume will be mounted. The container path cannot be a system directory, such as / or /var/run. Otherwise, the container may not function properly. You are advised to mount the volume to an empty directory. If the directory is not empty, ensure that there are no files affecting container startup in the directory. Otherwise, such files will be replaced, resulting in failures to start the container and create the workload. NOTICE: If the volume is mounted to a high-risk directory, you are advised to use an account with minimum permissions to start the container; otherwise, high-risk files on the host machine may be damaged. Permission Read-only: You can only read the data volumes in the path. Read/Write: You can modify the data volumes in the path. Newly written data is not migrated if the container is migrated, which may cause a data loss. Click Add Container Path to add multiple settings. Then, click OK.

1. Create a workload by referring to Creating a Deployment, Creating a StatefulSet, or Creating a DaemonSet. After you add a container, expand Data Storage, and click Add Local Volume.
2. Set the local volume type to ConfigMap and set parameters for adding a local volume, as shown in Table 3.

   Table 3 Setting parameters for mounting a ConfigMap volume

   Parameter	Description
   Type	Select ConfigMap.
   Option	Select the desired ConfigMap name. A ConfigMap must be created in advance. For details, see Creating a ConfigMap.
   Add Container Path	Configure the following parameters: subPath: Enter a subpath, for example, tmp. A subpath is used to mount a local disk so that the same data volume is used in a single pod. If this parameter is left blank, the root path is used by default. Container Path: Enter the path of the container, for example, /tmp. This parameter indicates the container path to which a data volume will be mounted. The container path cannot be a system directory, such as / or /var/run. Otherwise, the container may not function properly. You are advised to mount the volume to an empty directory. If the directory is not empty, ensure that there are no files affecting container startup in the directory. Otherwise, such files will be replaced, resulting in failures to start the container and create the workload. NOTICE: If the volume is mounted to a high-risk directory, you are advised to use an account with minimum permissions to start the container; otherwise, high-risk files on the host machine may be damaged. Set the permission to Read-only. Data volumes in the path are read-only. Click Add Container Path to add multiple settings. Then, click OK.

1. Create a workload by referring to Creating a Deployment, Creating a StatefulSet, or Creating a DaemonSet. After you add a container, expand Data Storage, and click Add Local Volume.
2. Set the local volume type to Secret and set parameters for adding a local volume, as shown in Table 4.

   Table 4 Setting parameters for mounting a secret volume

   Parameter	Description
   Type	Secret.
   Secret	Select the desired secret name. A secret must be created in advance. For details, see Creating a Secret.
   Add Container Path	Configure the following parameters: subPath: Enter a subpath, for example, tmp. A subpath is used to mount a local disk so that the same data volume is used in a single pod. If this parameter is left blank, the root path is used by default. Container Path: Enter the path of the container, for example, /tmp. This parameter indicates the container path to which a data volume will be mounted. The container path cannot be a system directory, such as / or /var/run. Otherwise, the container may not function properly. You are advised to mount the volume to an empty directory. If the directory is not empty, ensure that there are no files affecting container startup in the directory. Otherwise, such files will be replaced, resulting in failures to start the container and create the workload. NOTICE: If the volume is mounted to a high-risk directory, you are advised to use an account with minimum permissions to start the container; otherwise, high-risk files on the host machine may be damaged. Set the permission to Read-only. Data volumes in the path are read-only. Click Add Container Path to add multiple settings. Then, click OK.