检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
For clusters of v1.19.10 and later, if an HPA policy is used to scale out a workload with EVS volumes mounted, a new pod cannot be started because EVS disks cannot be attached. Procedure Log in to the CCE console and click the cluster name to access the cluster console.
The cloud storage type can be EVS or SFS. If no cloud storage is available, click Create PVC. If you select EVS, the AZ of the EVS disk must be the same as that of the node.
Such resources, which are created either manually or automatically during cluster creation, include ECSs, EVS disks, EIPs, bandwidth, and load balancers. For more pricing details, see Product Pricing Details.
Such resources, which are created either manually or automatically during cluster creation, include ECSs, EVS disks, EIPs, bandwidth, and load balancers. For more pricing details, see Product Pricing Details.
With everest-csi-controller and everest-csi-driver, you can use cloud storage services such as EVS, SFS, and OBS. $ kubectl get po --namespace=kube-system NAME READY STATUS RESTARTS AGE everest-csi-controller-6d796fb9c5-v22df 2/2 Running
Both the local PVs and local ephemeral volumes (EVs) are a volume group (VG) in LVM. VG used by the local PVs: vg-everest-localvolume-persistent VG used by the local EVs: vg-everest-localvolume-ephemeral This section describes how to restore a local PV.
CCE does not support EVS disks of the ReadWriteMany type. If resources of this type exist in the source cluster, change the storage type to ReadWriteOnce.
EVS Disks Table 7 EVS disks Operation Impact Solution Remarks Manually unmounting an EVS disk on the console An I/O error occurs when data is written into a pod. Delete the mount path from the node and schedule the pod again.
The price of the default flavor A (including the EVS disk price) is $0.0993 USD/hour, and the price of flavor B is $0.1923 USD/hour.
Store your service data in EVS disks, which are more reliable than local disks. General-purpose SSD V2 disks allow you to specify the disk IOPS and throughput. For details, see EVS performance data.
Store your service data in EVS disks, which are more reliable than local disks. General-purpose SSD V2 disks allow you to specify the disk IOPS and throughput. For details, see EVS performance data.
Changing the Billing Mode of a Node The billing modes of resources like EVS disks and EIPs used by pay-per-use nodes cannot be changed simultaneously. For details, see Pay-per-Use to Yearly/Monthly.
Using storage (such as EVS disks and file systems) can effectively prevent data loss caused by rebuilding of a container. This ensures that important data is persistently stored and can be used after the container is rebuilt. Parent Topic: Container Configuration
Changing the Billing Mode of a Node The billing modes of resources like EVS disks and EIPs used by pay-per-use nodes cannot be changed simultaneously. For details, see Pay-per-Use to Yearly/Monthly.
Do not modify information about resources created by CCE, such as security groups and EVS disks. Resources created by CCE are labeled cce. Deployment CCE cluster functions may be abnormal.
What Should I Do If I/O Suspension Occasionally Occurs When SCSI EVS Disks Are Used? What Should I Do If Excessive Docker Audit Logs Affect the Disk I/O? How Do I Fix an Abnormal Container or Node Due to No Thin Pool Disk Space?
Storage: CCE is integrated with multiple storage services like EVS, SFS, and OBS and provides disk encryption, snapshot, and backup capabilities.
Commercial use 6 Custom tags can be added to dynamically created EVS disks. When dynamically creating EVS PVCs, you can add TMS tags to automatically created EVS disks to classify resources. This facilitates cost management. Commercial use April 2023 No.
If you do not bring your account current before the retention period ends, CCE clusters and resources like nodes, EVS disks, and EIPs will be released and the data cannot be restored.
Notes and Constraints Local EVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is 1.2.29 or later. The first data disk (used by container runtime and the kubelet component) on a node cannot be imported as a storage pool.