检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Fault Locating Abnormal EVS Storage Volume Mounting Abnormal SFS Turbo Storage Volume Mounting Abnormal SFS Storage Volume Mounting Storage Volume Mounting Timed Out Abnormal EVS Storage Volume Mounting Symptom Possible Cause Solution Mounting an EVS volume to a StatefulSet times
EVS volumes: Mount an EVS volume to a container path. When the container is migrated, the mounted EVS volume is migrated together. This storage class is applicable when data needs to be stored permanently. OBS volumes: Create OBS volumes and mount them to a container path.
EVS volumes: Mount an EVS volume to a container path. When the container is migrated, the mounted EVS volume is migrated together. This storage class is applicable when data needs to be stored permanently. SFS volumes: Create SFS volumes and mount them to a container path.
Set this parameter based on the storage volume type. huawei.com/fuxivol (EVS) huawei.com/fuxinfs (SFS) huawei.com/fuxiobs (OBS) huawei.com/fuxiefs (SFS Turbo) fsType Yes String File system type. Set this parameter based on the storage volume type. ext4: EVS volume.
The following PVC types support usage monitoring: EVS PVCs (The value of volumeMode must be Filesystem.) Local PVCs (The Everest version installed in the cluster must be 2.4.41 or later.)
FlexVolume (Discarded) Introduction CCE Container Storage (FlexVolume), also called storage-driver, functions as a standard Kubernetes FlexVolume plugin to allow containers to use EVS, SFS, OBS, and SFS Turbo storage resources.
However, when using CCE, you may also be using other cloud services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Virtual Private Cloud (VPC), Elastic Load Balance (ELB), and SoftWare Repository for Containers (SWR). What Is Quota?
Creating a Deployment Creating a StatefulSet EVS EVS disks can be attached to cloud servers and scaled to a higher capacity whenever needed. In CCE, a node is an ECS with multiple EVS disks. You can specify the EVS disk size when creating a node.
Figure 3 Viewing the details of the EVS disk On the CCE console, click the cluster name to access the cluster console. Choose Nodes in the navigation pane, click the Nodes tab, and click Create Node to create a node in the same AZ as the EVS disk.
If no more than 20 EVS disks can be attached to a node, the node, already has one system disk and one data disk attached, can only accept up to 18 additional EVS disks.
You can use this cluster ID to obtain these EVS disks automatically created in the cluster and delete them as required. Go to the EVS console. Search for EVS disks by pvc-{UID} to get all automatically created EVS disks in the cluster. Press F12 to open the developer tools.
Volume Service (EVS) Pay-per-use recommended EVS disk specification: 100 GiB EVS disk type: General purpose SSD 1 USD0.0157/hour Load Balancer (ELB) Pay-per-use recommended Type: Shared Billed By: Traffic Bandwidth: 5 Mbit/s 1 USD0.053/hour + USD0.114/GB (The traffic fee is charged
For details about how to configure an EVS disk, see Purchasing an EVS Disk. The specifications and space of the new disk must be the same as those configured for the target node pool. You need also select SCSI for Advanced Settings.
Volume Service (EVS) Pay-per-use recommended EVS disk specification: 100 GiB EVS disk type: General purpose SSD 1 USD0.0157/hour Parent Topic: Containerizing an Enterprise Application (ERP)
EVS csi.storage.k8s.io/fstype Yes If an EVS disk is used, the parameter value can be ext4. EVS everest.io/disk-volume-type Yes EVS disk type. All letters are in uppercase.
Yearly/Monthly or pay-per-use Unit price of an EVS disk x EVS disk capacity x Required duration For details, see EVS Pricing Details. (Optional) EIP: To access the Internet from a node, you need to purchase an EIP.
Ephemeral volumes (EVs) in Kubernetes are designed for the above scenario. EVs are created and deleted together with pods following the pod lifecycle.
Why Does a PV Fail to Be Mounted to a Pod After the PV Is Re-bound to a Released EVS Disk?
Concurrent EVS Disk Attaching Tasks Visualized GUI configuration Number of workers that can be concurrently processed by Everest for attaching EVS volumes. The default value is 60.
EVS disk If an EVS disk (a system disk or a data disk) is created along with a pay-per-use ECS, the EVS disk is also billed on a pay-per-use basis.
