检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
StatefulSets support dynamic attachment of EVS disks. For details, see Dynamically Mounting an EVS Disk to a StatefulSet or Dynamically Mounting a Local PV to a StatefulSet.
Storage Expanding the Storage Space Mounting Object Storage Across Accounts Dynamically Creating an SFS Turbo Subdirectory Using StorageClass Changing the Storage Class Used by a Cluster of v1.15 from FlexVolume to CSI Everest Using Custom Storage Classes Scheduling EVS Disks Across
Key Capabilities Diverse cost types: Both the management costs of CCE clusters and the costs of ECS and EVS resources associated with each CCE cluster are analyzed and displayed.
EVS disks (including system disks and data disks) The billing mode of the system disks and data disks attached to a node cannot be changed on the EVS console. You need to change their billing modes together with the node on the CCE console.
You need to pay attention to the following: You will not be billed for the management of the cluster, but other cloud service resources like EVS disks and bandwidth in the cluster will still be billed in their own billing modes.
That is, volumeID and storageType must be configured at the same time. bs: EVS nfs: SFS obs: OBS efs: SFS Turbo accessModes Array of strings Access mode of the volume. Only the first value in all selected options is valid.
disks EVS disks can be attached to cloud servers and scaled to a higher capacity whenever needed.
*:* None Perform all operations on Elastic Volume Service (EVS).
In this example, the EVS disk is used. You can change the storage type as required. Create the pvc.yaml file.
What Should I Do If I/O Suspension Occasionally Occurs When SCSI EVS Disks Are Used? How Do I Fix an Abnormal Container or Node Due to No Thin Pool Disk Space? How Do I Rectify Failures When the NVIDIA Driver Is Used to Start Containers on GPU Nodes? Parent topic: Node
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.
To expand the thin pool size, 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.
1 # Region where the EVS disk is in failure-domain.beta.kubernetes.io/zone: # AZ where the EVS disk is in.
Therefore, the storage resources in the CCE cluster should be EVS volumes, and the backend storage media should be SAS disks.
That is, volumeID and storageType must be configured at the same time. bs: EVS nfs: SFS obs: OBS efs: SFS Turbo accessModes Array of strings Access mode of the volume. Only the first value in all selected options is valid.
That is, volumeID and storageType must be configured at the same time. bs: EVS nfs: SFS obs: OBS efs: SFS Turbo accessModes Array of strings Access mode of the volume. Only the first value in all selected options is valid.
Renewing a Subscription in Billing Center This method is suitable for all resources, including clusters, nodes, EVS disks, and EIPs. Go to the Renewals page. Customize the search criteria.
- metadata: name: disk-csi spec: accessModes: [ "ReadWriteOnce" ] # EVS disks can only be mounted to and accessed by a single node in read/write mode, that is, ReadWriteOnce.
This is because EVS disks cannot be attached to nodes in different AZs from the EVS disks. For example, a workload pod with an EVS volume that is in AZ 1 cannot be scheduled to a node in AZ 2.
In CCE, the Everest add-on is installed by default in clusters of Kubernetes v1.15 or later to access storage services such as EVS, SFS, OBS, and SFS Turbo.