检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
CCE supports the following container storage classes: local disk storage, EVS disks, SFS file systems, OBS buckets, SFS Turbo file systems, snapshots, and backups.
Storage EVS disks can be used as storage. Set the following parameters following instructions: AZ: Set this parameter based on the site requirements. An AZ is a physical region where resources use independent power supply and networks.
Pods can use local EVs to buffer data and store logs, or mount emptyDir volumes to containers. For details, see Local ephemeral storage.
quotas:get and evs:types:get.
Only the EVS disk capacity can be adjusted. (Local disks are available only when the node specification is disk-intensive or Ultra-high I/O.)
Cost effective You only pay for the control plane nodes and the infrastructure resources (such as cloud servers, EVS disks, EIPs, bandwidth, and load balancers) used to store and run applications. Why Containerization? Docker is written in Go, a language designed by Google.
For example, CCE can be interconnected with block storage (EVS), file storage (SFS), and object storage (OBS) services. Basic Objects in Kubernetes The following figure shows the basic objects in Kubernetes and the relationships between them.
StorageClass: EVS, SFS, SFS Turbo, OBS, DSS, local PV, and EV are provided. For details, see Storage Overview. Auto scaling Workload scaling: The number of workload pods can be adjusted based on service requirements and policies. For details, see Workload Scaling Rules.
EVS snapshot backup Master node disks, including component images, configurations, logs, and etcd data One-click backup on a web page (manually triggered) 1-5 minutes 20 minutes This function is coming soon.
If the Prometheus data source is used, you may need to create some EVS disks. For details, see Price Calculator. Step 5: Disable NPU-Exporter (Optional) To disable NPU-Exporter after use, take this step.
When the creation is complete: The image creation process uses certain charging resources, including ECSs, EVS disks, EIPs, bandwidth, and IMS images. These resources are automatically released when the image is successfully created or fails to be created.
There is remaining EVS disk quota. When a node is reset, the backend will make it unschedulable. Resetting a node will clear the Kubernetes labels and taints you added (those added by editing a node pool will not be lost).
If the workload contains more than one pod, EVS volumes cannot be mounted. (Optional) Logging: Report standard container output logs to AOM by default, without requiring manual settings. You can manually configure the log collection path.
External Dependencies Scenario Diagnosis Item Enabling Monitoring Center Rectification Solution Resource quotas of a node Whether 90% or more of the EVS disk quota has been used Yes Sufficient resource quotas are required for node creation in a cluster.
If the workload contains more than one pod, EVS volumes cannot be mounted. (Optional) Security Context: Assign container permissions to protect the system and other containers from being affected.
Typical scenario: EVS disks have slow I/Os due to network fluctuation.
Storage You can only create EVS disks in edge regions. Service and ingress Only dedicated load balancers are supported.
Configuring resource quotas for cloud services: Cloud services like ECS, EVS, VPC, ELB, and SWR are also used to run the CCE clusters. If the existing resource quotas cannot meet your requirements, submit a service ticket to increase the quotas.
Clearing Idle Resources in a Timely Manner It is a good option to identify and clear idle cloud services or resources in clusters in a timely manner, such as unused ECSs, EVS disks, OBS buckets, ELB load balancers, and EIPs.
The EVS disk type (csi-disk) is used, with a size of 10 GiB. WordPress requires no data persistence, so you can set persistence.enabled to false for the PV.
