检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
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. Data disks used by the container runtime and Kubernetes components cannot be imported into a storage pool.
Solution 2: Expanding the disk capacity To expand a disk capacity, perform the following operations: Expand the capacity of a data disk on the EVS console. For details, see Expanding EVS Disk Capacity. Only the storage capacity of EVS disks can be expanded.
The prerequisite is that CCE has obtained the permissions for accessing services such as Elastic Volume Service (EVS), Scalable File Service (SFS), and Object Storage Service (OBS).
Local data storage must be enabled in Cloud Native Cluster Monitoring, which may incur EVS disk fees. For details, see Elastic Volume Service Price Calculator. A public LoadBalancer Service must be created in the cluster. This will incur ELB billing.
Figure 3 Multi-dimension cluster costs Parameter Description Namespace Total Namespace Cost indicates the total cost (CPU cost, memory cost, and EVS cost) of the workloads in each selected namespace.
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.
Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared within the same region.
The EVS is used as an example to describe how to dynamically provision a PV for a ClickHouse cluster. The VolumeClaimTemplate can only be used to provision EVS disks and local PVs to StatefulSets. Create a StorageClass.
Solution 2: Expanding the disk capacity To expand a disk capacity, perform the following operations: Expand the capacity of a data disk on the EVS console. For details, see Expanding EVS Disk Capacity. Only the storage capacity of EVS disks can be expanded.
Enabling Auto-Renewal on the Renewals Page This method is suitable for all resources, including clusters, nodes, EVS disks, and EIPs. Go to the Renewals page. Customize the search criteria.
Options: Only evs (EVS disks), local (local disks), and system (system disks) are supported.
When EVS disk snapshots are used for backup, only EVS PVs are supported and the snapshot constraints apply (for example, cross-AZ restoration is not supported). The pricing is the same as EVS disk snapshots.
EVS Disk Bandwidth (Gbit/s) Max.
PV Type Associated Underlying Storage Whether to Delete Underlying Storage EVS Disks Yes DSS Disks Yes SFS SFS Capacity-Oriented or general purpose file system (SFS 3.0 Capacity-Oriented) Yes OBS OBS buckets or parallel file systems Yes SFS Turbo SFS Turbo file systems Yes Local PV
That means that volumeID and storageType must be configured concurrently. bs: EVS nfs: SFS 1.0 obs: OBS efs: SFS Turbo accessModes Array of strings Access mode of the volume. Only the first value in all selected options is valid.
Key: can be DisplayPreCheckDetail (displaying details about all cluster check items before an upgrade), EvsSnapshot (using EVS snapshots to back up clusters), LabelForSkippedNode (labeling the nodes skipped during a cluster upgrade), or UpgradeStrategy (specifying cluster upgrade
There is no available EVS disk flavor for the node. Change to another available EVS disk flavor or contact technical support. 400 CCE.01400023 operation conflict Nodes cannot be created during cluster scale-out.
quotas:get Queries EVS disk quotas. ecs:cloudServerQuotas:get Queries tenant quotas. apm:icmgr:get Obtains AOM 2.0 permissions. apm:icmgr:create Grants AOM 2.0 permissions.
Options: Only evs (EVS disks), local (local disks), and system (system disks) are supported.
Options: Only evs (EVS disks), local (local disks), and system (system disks) are supported.
