On this page

Show all

Help Center/ Cloud Container Engine_Autopilot/ User Guide/ Storage/ EVS Volumes/ Using an EVS Disk Through a Dynamic PV

Using an EVS Disk Through a Dynamic PV

Updated on 2025-02-27 GMT+08:00

View PDF

CCE Autopilot allows you to dynamically create storage volumes from EVS disks by specifying a StorageClass when no EVS disks are available.

Prerequisites

You have created a cluster.
If you want to create a cluster by running commands, kubectl has been used to connect to the cluster. For details, see Connecting to a Cluster Using kubectl.

Constraints

Not all regions support EVS volumes. View the regions where EVS volumes are supported on the console. You can also view Function Overview to learn about all regions where EVS volumes are supported.
EVS disks cannot be used by multiple workloads, multiple pods of the same workload, or multiple tasks. If EVS disks are used when you create a Deployment, select only one pod for the Deployment.

The cluster version must be v1.27.8-r0, v1.28.6-r0, or later. If the cluster version does not meet the requirements, you need to upgrade the cluster.
No more than 10 EVS disks can be attached to each workload in a cluster. If more than 10 EVS disks are attached, the workload may run abnormally.

Resource tags can be added to dynamically created EVS disks. After they are created, the resource tags cannot be updated on the CCE console. To update them, go to the EVS console. If you use an existing EVS disk to create a PV, you also need to add or update resource tags on the EVS console.

Dynamically Creating EVS Volumes

Specify StorageClass to automatically create EVS disks and storage volumes and mount the volumes to workloads for persistent storage on the console or using kubectl.

Using the CCE Console
Using kubectl

Dynamically create a PVC and PV.

In the navigation pane on the left, choose Storage. Then click the PVCs tab. In the upper right corner, click Create PVC. In the displayed dialog box, configure the parameters.

Figure 1 Creating a PVC
Click to enlarge

Parameter	Description
PVC Type	In this example, select EVS.
PVC Name	Enter the PVC name, which must be unique in the same namespace.
Namespace	A namespace is a conceptual grouping of resources or objects. Each namespace provides isolation for data from other namespaces. After a cluster is created, the default namespace is created by default. If there is no special requirement, select the default namespace.
Creation Method	If no underlying storage is available, select Dynamically provision to create a PVC, PV, and underlying storage on the console in cascading mode. If underlying storage is available, select either Use existing or Create new. For details about static creation, see Using an Existing EVS Disk Through a Static PV. In this example, select Dynamically provision.
Storage Classes	The StorageClass for EVS volumes is csi-disk.
(Optional) PV Name Prefix	This parameter specifies the name of the underlying storage that is automatically created. The actual underlying storage name is in the format of "PV name prefix + PVC UID". If this parameter is left blank, the default prefix pvc will be used. For example, if the storage volume name prefix is set to test, the actual underlying storage name is test-{UID}.
AZ	Select the AZ of the EVS disk. After the EVS disk is created, the AZ cannot be changed. In this example, select AZ3.
Disk Type	Select an EVS disk type. EVS disk types vary depending on regions. Obtain the available EVS types on the console. In this example, select High I/O. NOTE: General-purpose SSD V2 disks allow you to specify the disk IOPS and throughput. For details, see EVS performance data.
Capacity (GiB)	Capacity of the requested storage volume. Set it to 10 in this example.
Access Mode	EVS volumes support only ReadWriteOnce, indicating that a storage volume can only be mounted to one pod in read/write mode. For details, see Volume Access Modes.
Encryption	Configure whether to encrypt underlying storage. If you select Enabled (key), an encryption key must be configured. Currently, encryption is not supported.
Enterprise Project	The default enterprise project, the enterprise project to which the cluster belongs, or the enterprise project specified by StorageClass is available.
Resource Tag	You can add resource tags to classify resources. You can create predefined tags on the TMS console. The predefined tags are available to all resources that support tags. You can use predefined tags to improve the tag creation and resource migration efficiency. For details, see Creating Predefined Tags. CCE automatically creates system tags CCE-Cluster-ID={Cluster ID}, CCE-Cluster-Name={Cluster name}, and CCE-Namespace={Namespace name}. These tags cannot be modified. NOTE: After a dynamic PV of the EVS type is created, the resource tags cannot be updated on the CCE console. To update these resource tags, go to the EVS console.

Click Create.
In the navigation pane on the left, choose Storage. View the created PVC and PV on the PVCs and PVs tabs, respectively.

Create a workload.

In the navigation pane on the left, choose Workloads. Then click the StatefulSets tab.

In the upper right corner, click Create Workload. On the displayed page, click Data Storage in the Container Settings area and click Add Volume to select PVC.

Table 1 describes the parameters for mounting the volume. For details about other parameters, see Workloads.

In this example, the volume is mounted to the /data path of the container. The container data generated in this path is stored in the EVS disk.

NOTE:

A non-shared EVS disk can be mounted to only one pod. If there are multiple pods, extra pods cannot start normally. Ensure that the number of pods for running a workload is 1 if an EVS disk is mounted.

Figure 2 Parameters for mounting a storage volume
Click to enlarge

**Table 1** Parameters for mounting a storage volume
Parameter	Description
PVC	Select an existing EVS volume. An EVS volume can only be mounted to one workload.
Mount Path	Enter a mount path, for example, /data. This parameter indicates the container path that the volume will be mounted to. Do not mount the volume to a system directory such as / or /var/run. This may cause container errors. Mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. If there are such files, they will be replaced, which will lead to a container startup or workload creation failure. NOTICE: If a volume is mounted to a high-risk directory, use an account with minimum permissions to start the container, or high-risk files on the host may be damaged.
Subpath	Enter the subpath of the storage volume and mount a path in the storage volume to the container. In this way, different folders of the same storage volume can be used in a single pod. data, for example, indicates that data in the mount path of the container is stored in the data directory of the storage volume. If this parameter is left blank, the root path is used by default.
Permission	Read-only: You can only read the data in the mounted volume. Read-write: You can modify the volume mounted to the path. Newly written data will not be migrated if the container is migrated, which may cause data loss.

Configure other parameters and click Create Workload.
After the workload is created, the data in the container mount directory will be persistently stored. Verify the storage by referring to Verifying Data Persistence.

Use kubectl to connect to the cluster.

Use StorageClass to dynamically create a PVC and PV.

Create the pvc-evs-auto.yaml file.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc-evs-auto
  namespace: default
  annotations:
      everest.io/disk-volume-type: SAS    # EVS disk type
    everest.io/enterprise-project-id: <your_project_id>  # (Optional) Enterprise project ID. If an enterprise project is specified, use the same enterprise project when creating a PVC. Otherwise, the PVC cannot be bound to a PV.

    everest.io/disk-volume-tags: '{"key1":"value1","key2":"value2"}' # (Optional) Custom resource tags

    everest.io/disk-iops: '3000'      # (Optional) IOPS of only a GPSSD2 EVS disk
    everest.io/disk-throughput: '125' # (Optional) Throughput of only a GPSSD2 EVS disk

    everest.io/csi.volume-name-prefix: test  # (Optional) Storage volume name prefix of the automatically created underlying storage

  labels:
    failure-domain.beta.kubernetes.io/region: <your_region>   # Replace the region with the one where the cluster is located.
    failure-domain.beta.kubernetes.io/zone: <your_zone>       # Replace the AZ with the one where the EVS disk is located.
spec:
  accessModes:
  - ReadWriteOnce               # The value must be ReadWriteOnce for EVS disks.
  resources:
    requests:
      storage: 10Gi             # EVS disk capacity, in GiB. The value ranges from 1 to 32768.
  storageClassName: csi-disk    # The StorageClass of the EVS disk

**Table 2** Key parameters
Parameter	Mandatory	Description
failure-domain.beta.kubernetes.io/region	Yes	Region of the cluster. For example, cn-east-3. For details, see Regions and Endpoints.
failure-domain.beta.kubernetes.io/zone	Yes	AZ of the EVS disk. You can obtain all supported AZs by querying the AZ list.
everest.io/disk-volume-type	Yes	EVS disk type. All letters are in uppercase. EVS disk types vary depending on regions. Obtain the available EVS types on the console. SAS: high I/O SSD: ultra-high I/O GPSSD: general-purpose SSD ESSD: extreme SSD GPSSD2: general-purpose SSD v2. You need to specify the everest.io/disk-iops and everest.io/disk-throughput annotations.
everest.io/disk-iops	No	Preconfigured IOPS, which is supported only by general-purpose SSD v2 EVS disks. The IOPS of general-purpose SSD v2 EVS disks ranges from 3000 to 128000, and the maximum value is 500 times of the capacity (GiB). If the IOPS of general-purpose SSD v2 disks is greater than 3000, extra IOPS will be billed. For details, see Price Calculator.
everest.io/disk-throughput	No	Preconfigured throughput, which is supported only by general-purpose SSD v2 EVS disks. The value ranges from 125 MiB/s to 1,000 MiB/s. The maximum value is a quarter of IOPS. If the throughput is greater than 125 MiB/s, extra throughput will be billed. For details, see Price Calculator.
everest.io/enterprise-project-id	No	Enterprise project ID of the EVS disk. This parameter is optional. If an enterprise project is specified, use the same enterprise project when creating a PVC, or the PVC cannot be bound to a PV. To obtain an enterprise project ID, log in to the EPS console, click the name of the target enterprise project, and copy the enterprise project ID.
everest.io/disk-volume-tags	No	You can add resource tags to classify resources. This field is optional. You can create predefined tags on the TMS console. The predefined tags are available to all resources that support tags. You can use predefined tags to improve the tag creation and resource migration efficiency. For details, see Creating Predefined Tags. CCE automatically creates system tags CCE-Cluster-ID={Cluster ID}, CCE-Cluster-Name={Cluster name}, and CCE-Namespace={Namespace name}. These tags cannot be modified.
everest.io/csi.volume-name-prefix	No	This parameter is optional. It specifies the name of the underlying storage that is automatically created. The actual underlying storage name is in the format of "PV name prefix + PVC UID". If this parameter is left blank, the default prefix pvc will be used. Enter 1 to 26 characters that cannot start or end with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed. For example, if the storage volume name prefix is set to test, the actual underlying storage name is test-{UID}.
storage	Yes	Requested PVC capacity, in Gi. The value ranges from 1 to 32768.
storageClassName	Yes	The StorageClass for EVS volumes is csi-disk.

Run the following command to create a PVC:
```
kubectl apply -f pvc-evs-auto.yaml
```

Create a workload.

Create a file named web-evs-auto.yaml. In this example, the EVS volume is mounted to the /data path.

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: web-evs-auto
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: web-evs-auto
  serviceName: web-evs-auto   # Headless Service name
  template:
    metadata:
      labels:
        app: web-evs-auto
    spec:
      containers:
      - name: container-1
        image: nginx:latest
        volumeMounts:
        - name: pvc-disk    # Volume name, which must be the same as the volume name in the volumes field.
          mountPath: /data  #Location where the storage volume is mounted.
      imagePullSecrets:
        - name: default-secret
      volumes:
        - name: pvc-disk    # Custom volume name
          persistentVolumeClaim:
            claimName: pvc-evs-auto    # Name of the created PVC.
---
apiVersion: v1
kind: Service
metadata:
  name: web-evs-auto   # Headless Service name
  namespace: default
  labels:
    app: web-evs-auto
spec:
  selector:
    app: web-evs-auto
  clusterIP: None
  ports:
    - name: web-evs-auto
      targetPort: 80
      nodePort: 0
      port: 80
      protocol: TCP
  type: ClusterIP

Run the following command to create a workload that the EVS volume is mounted to:
```
kubectl apply -f web-evs-auto.yaml
```
After the workload is created, the data in the container mount directory will be persistently stored. Verify the storage by referring to Verifying Data Persistence.

Dynamically create a PVC and PV.

In the navigation pane on the left, choose Storage. Then click the PVCs tab. In the upper right corner, click Create PVC. In the displayed dialog box, configure the parameters.

Figure 1 Creating a PVC
Click to enlarge

Parameter	Description
PVC Type	In this example, select EVS.
PVC Name	Enter the PVC name, which must be unique in the same namespace.
Namespace	A namespace is a conceptual grouping of resources or objects. Each namespace provides isolation for data from other namespaces. After a cluster is created, the default namespace is created by default. If there is no special requirement, select the default namespace.
Creation Method	If no underlying storage is available, select Dynamically provision to create a PVC, PV, and underlying storage on the console in cascading mode. If underlying storage is available, select either Use existing or Create new. For details about static creation, see Using an Existing EVS Disk Through a Static PV. In this example, select Dynamically provision.
Storage Classes	The StorageClass for EVS volumes is csi-disk.
(Optional) PV Name Prefix	This parameter specifies the name of the underlying storage that is automatically created. The actual underlying storage name is in the format of "PV name prefix + PVC UID". If this parameter is left blank, the default prefix pvc will be used. For example, if the storage volume name prefix is set to test, the actual underlying storage name is test-{UID}.
AZ	Select the AZ of the EVS disk. After the EVS disk is created, the AZ cannot be changed. In this example, select AZ3.
Disk Type	Select an EVS disk type. EVS disk types vary depending on regions. Obtain the available EVS types on the console. In this example, select High I/O. NOTE: General-purpose SSD V2 disks allow you to specify the disk IOPS and throughput. For details, see EVS performance data.
Capacity (GiB)	Capacity of the requested storage volume. Set it to 10 in this example.
Access Mode	EVS volumes support only ReadWriteOnce, indicating that a storage volume can only be mounted to one pod in read/write mode. For details, see Volume Access Modes.
Encryption	Configure whether to encrypt underlying storage. If you select Enabled (key), an encryption key must be configured. Currently, encryption is not supported.
Enterprise Project	The default enterprise project, the enterprise project to which the cluster belongs, or the enterprise project specified by StorageClass is available.
Resource Tag	You can add resource tags to classify resources. You can create predefined tags on the TMS console. The predefined tags are available to all resources that support tags. You can use predefined tags to improve the tag creation and resource migration efficiency. For details, see Creating Predefined Tags. CCE automatically creates system tags CCE-Cluster-ID={Cluster ID}, CCE-Cluster-Name={Cluster name}, and CCE-Namespace={Namespace name}. These tags cannot be modified. NOTE: After a dynamic PV of the EVS type is created, the resource tags cannot be updated on the CCE console. To update these resource tags, go to the EVS console.

Click Create.
In the navigation pane on the left, choose Storage. View the created PVC and PV on the PVCs and PVs tabs, respectively.

Create a workload.

In the navigation pane on the left, choose Workloads. Then click the StatefulSets tab.

In the upper right corner, click Create Workload. On the displayed page, click Data Storage in the Container Settings area and click Add Volume to select PVC.

Table 1 describes the parameters for mounting the volume. For details about other parameters, see Workloads.

In this example, the volume is mounted to the /data path of the container. The container data generated in this path is stored in the EVS disk.

NOTE:

Figure 2 Parameters for mounting a storage volume
Click to enlarge

**Table 1** Parameters for mounting a storage volume
Parameter	Description
PVC	Select an existing EVS volume. An EVS volume can only be mounted to one workload.
Mount Path	Enter a mount path, for example, /data. This parameter indicates the container path that the volume will be mounted to. Do not mount the volume to a system directory such as / or /var/run. This may cause container errors. Mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. If there are such files, they will be replaced, which will lead to a container startup or workload creation failure. NOTICE: If a volume is mounted to a high-risk directory, use an account with minimum permissions to start the container, or high-risk files on the host may be damaged.
Subpath	Enter the subpath of the storage volume and mount a path in the storage volume to the container. In this way, different folders of the same storage volume can be used in a single pod. data, for example, indicates that data in the mount path of the container is stored in the data directory of the storage volume. If this parameter is left blank, the root path is used by default.
Permission	Read-only: You can only read the data in the mounted volume. Read-write: You can modify the volume mounted to the path. Newly written data will not be migrated if the container is migrated, which may cause data loss.

Configure other parameters and click Create Workload.
After the workload is created, the data in the container mount directory will be persistently stored. Verify the storage by referring to Verifying Data Persistence.

Use kubectl to connect to the cluster.

Use StorageClass to dynamically create a PVC and PV.

Create the pvc-evs-auto.yaml file.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc-evs-auto
  namespace: default
  annotations:
      everest.io/disk-volume-type: SAS    # EVS disk type
    everest.io/enterprise-project-id: <your_project_id>  # (Optional) Enterprise project ID. If an enterprise project is specified, use the same enterprise project when creating a PVC. Otherwise, the PVC cannot be bound to a PV.

    everest.io/disk-volume-tags: '{"key1":"value1","key2":"value2"}' # (Optional) Custom resource tags

    everest.io/disk-iops: '3000'      # (Optional) IOPS of only a GPSSD2 EVS disk
    everest.io/disk-throughput: '125' # (Optional) Throughput of only a GPSSD2 EVS disk

    everest.io/csi.volume-name-prefix: test  # (Optional) Storage volume name prefix of the automatically created underlying storage

  labels:
    failure-domain.beta.kubernetes.io/region: <your_region>   # Replace the region with the one where the cluster is located.
    failure-domain.beta.kubernetes.io/zone: <your_zone>       # Replace the AZ with the one where the EVS disk is located.
spec:
  accessModes:
  - ReadWriteOnce               # The value must be ReadWriteOnce for EVS disks.
  resources:
    requests:
      storage: 10Gi             # EVS disk capacity, in GiB. The value ranges from 1 to 32768.
  storageClassName: csi-disk    # The StorageClass of the EVS disk

**Table 2** Key parameters
Parameter	Mandatory	Description
failure-domain.beta.kubernetes.io/region	Yes	Region of the cluster. For example, cn-east-3. For details, see Regions and Endpoints.
failure-domain.beta.kubernetes.io/zone	Yes	AZ of the EVS disk. You can obtain all supported AZs by querying the AZ list.
everest.io/disk-volume-type	Yes	EVS disk type. All letters are in uppercase. EVS disk types vary depending on regions. Obtain the available EVS types on the console. SAS: high I/O SSD: ultra-high I/O GPSSD: general-purpose SSD ESSD: extreme SSD GPSSD2: general-purpose SSD v2. You need to specify the everest.io/disk-iops and everest.io/disk-throughput annotations.
everest.io/disk-iops	No	Preconfigured IOPS, which is supported only by general-purpose SSD v2 EVS disks. The IOPS of general-purpose SSD v2 EVS disks ranges from 3000 to 128000, and the maximum value is 500 times of the capacity (GiB). If the IOPS of general-purpose SSD v2 disks is greater than 3000, extra IOPS will be billed. For details, see Price Calculator.
everest.io/disk-throughput	No	Preconfigured throughput, which is supported only by general-purpose SSD v2 EVS disks. The value ranges from 125 MiB/s to 1,000 MiB/s. The maximum value is a quarter of IOPS. If the throughput is greater than 125 MiB/s, extra throughput will be billed. For details, see Price Calculator.
everest.io/enterprise-project-id	No	Enterprise project ID of the EVS disk. This parameter is optional. If an enterprise project is specified, use the same enterprise project when creating a PVC, or the PVC cannot be bound to a PV. To obtain an enterprise project ID, log in to the EPS console, click the name of the target enterprise project, and copy the enterprise project ID.
everest.io/disk-volume-tags	No	You can add resource tags to classify resources. This field is optional. You can create predefined tags on the TMS console. The predefined tags are available to all resources that support tags. You can use predefined tags to improve the tag creation and resource migration efficiency. For details, see Creating Predefined Tags. CCE automatically creates system tags CCE-Cluster-ID={Cluster ID}, CCE-Cluster-Name={Cluster name}, and CCE-Namespace={Namespace name}. These tags cannot be modified.
everest.io/csi.volume-name-prefix	No	This parameter is optional. It specifies the name of the underlying storage that is automatically created. The actual underlying storage name is in the format of "PV name prefix + PVC UID". If this parameter is left blank, the default prefix pvc will be used. Enter 1 to 26 characters that cannot start or end with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed. For example, if the storage volume name prefix is set to test, the actual underlying storage name is test-{UID}.
storage	Yes	Requested PVC capacity, in Gi. The value ranges from 1 to 32768.
storageClassName	Yes	The StorageClass for EVS volumes is csi-disk.

Run the following command to create a PVC:
```
kubectl apply -f pvc-evs-auto.yaml
```

Create a workload.

Create a file named web-evs-auto.yaml. In this example, the EVS volume is mounted to the /data path.

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: web-evs-auto
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: web-evs-auto
  serviceName: web-evs-auto   # Headless Service name
  template:
    metadata:
      labels:
        app: web-evs-auto
    spec:
      containers:
      - name: container-1
        image: nginx:latest
        volumeMounts:
        - name: pvc-disk    # Volume name, which must be the same as the volume name in the volumes field.
          mountPath: /data  #Location where the storage volume is mounted.
      imagePullSecrets:
        - name: default-secret
      volumes:
        - name: pvc-disk    # Custom volume name
          persistentVolumeClaim:
            claimName: pvc-evs-auto    # Name of the created PVC.
---
apiVersion: v1
kind: Service
metadata:
  name: web-evs-auto   # Headless Service name
  namespace: default
  labels:
    app: web-evs-auto
spec:
  selector:
    app: web-evs-auto
  clusterIP: None
  ports:
    - name: web-evs-auto
      targetPort: 80
      nodePort: 0
      port: 80
      protocol: TCP
  type: ClusterIP

Run the following command to create a workload that the EVS volume is mounted to:
```
kubectl apply -f web-evs-auto.yaml
```
After the workload is created, the data in the container mount directory will be persistently stored. Verify the storage by referring to Verifying Data Persistence.

Verifying Data Persistence

View the deployed application and files stored in the EVS volume.
1. Run the following command to view the pod:
```
kubectl get pod | grep web-evs-auto
```
  Expected output:
```
web-evs-auto-0                  1/1     Running   0               38s
```
2. Run the following command to verify that the EVS volume has been mounted to the /data path:
```
kubectl exec web-evs-auto-0 -- df | grep data
```
  Expected output:
```
/dev/sdc              10255636     36888  10202364   0% /data
```
3. Run the following command to view the created file in the /data path:
```
kubectl exec web-evs-auto-0 -- ls /data
```
  Expected output:
```
lost+found
```
Run the following command to create a file named static in the /data path:
```
kubectl exec web-evs-auto-0 --  touch /data/static
```
Run the following command to view the created file in the /data path:
```
kubectl exec web-evs-auto-0 -- ls /data
```
Expected output:
```
lost+found
static
```
Run the following command to delete the pod named web-evs-auto-0:
```
kubectl delete pod web-evs-auto-0
```
Expected output:
```
pod "web-evs-auto-0" deleted
```
The StatefulSet controller automatically creates a replica with the same name as the pod. Run the following command to check whether the file in the /data path has been modified:
```
kubectl exec web-evs-auto-0 -- ls /data
```
Expected output:
```
lost+found
static
```
The static file is retained, indicating that the data can be stored persistently.

Related Operations

You can also perform the operations described in Table 3.

**Table 3** Related operations
Operation	Description	Procedure
Expanding the capacity of an EVS volume	Quickly expand the capacity of a mounted EVS volume on the CCE console.	In the navigation pane on the left, choose Storage. Then click the PVCs tab. Locate the target PVC and click More > Scale-out in the Operation column. Enter the capacity to be added and click OK.
Viewing events	You can view event names, event types, number of occurrences, Kubernetes events, first occurrence time, and last occurrence time of the PVC or PV.	In the navigation pane on the left, choose Storage. Then click the PVCs or PVs tab. Locate the target PVC or PV, click View Events in the Operation column to view events generated within one hour (events are retained for one hour).
Viewing a YAML file	You can view, copy, and download the YAML files of a PVC or PV.	In the navigation pane on the left, choose Storage. Then click the PVCs or PVs tab. Locate the target PVC or PV, click View YAML in the Operation column to view or download the YAML.

Parent Topic: EVS Volumes

Previous topic: Using an Existing EVS Disk Through a Static PV

Next topic: Dynamically Mounting an EVS Volume to a StatefulSet

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot