检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
For details, see ECS Event Overview. Scenarios During ECS event handling, the ECS may be unavailable, which makes the node and pods cannot run properly.
Changing the ECS Group of an ECS The ECS group of the ECS to be managed must be the same as that of the target node pool. For more operation guides, see Managing ECS Groups. Log in to the ECS console. In the navigation pane, choose Elastic Cloud Server > ECS Group.
Symptom After successful login to the ECS node where the CCE cluster runs, it is found that there are a large number of CCE Node Problem Detector processes exist. Solution Upgrade the CCE Node Problem Detector add-on to the latest version.
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?
If the resources of the ECS flavor cannot meet service requirements, use ECSs of another flavor. If the ECS or memory quota is insufficient, increase the quota. If the ECS capacity verification fails, perform the verification again. Parent Topic: Node Pool
If a node fails to be connected to the Internet, perform the following operations: Check Item 1: Whether an EIP Has Been Bound to the Node Log in to the ECS console and check whether an EIP has been bound to the ECS corresponding to the node.
If you forget your key pair or password, you can log in to the ECS console to reset the password of the node. After the password is reset, you can log in to the node using the password. Procedure Log in to the ECS console.
When an ECS is accepted for management, the ECS OS will be reset to the standard image provided by CCE to ensure node stability.
Click the name of the node to display the ECS details page. In the upper right corner of the ECS details page, click Stop. After the ECS is stopped, choose More > Modify Specifications.
If you purchase both a data disk and an EIP when creating a spot price ECS, the data disk and EIP will be released when the ECS is released. If you attach data disks or bind EIPs to an existing spot price ECS, these resources must be manually released after the ECS is deleted.
Before you log in to a node (an ECS) using SSH through the Internet, ensure that the ECS already has an EIP bound. Only login to a running ECS is allowed. Only the user root can log in to a Linux server.
Click the Overview tab, click Expand, and check the ECS group to which the node pool belongs. Log in to the ECS console. In the navigation pane, choose Elastic Cloud Server > ECS Group and see if the target ECS group is present.
Common ECS information to be modified: ECS (node) name: Changing an ECS Name Node specifications: General Operations for Modifying Specifications Notes and Constraints Data, including the VM status, ECS names, number of CPUs, size of memory, ECS specifications, and public IP addresses
If you purchase both a data disk and an EIP when creating a spot pricing ECS, they will be automatically released when the ECS is released. If you attach data disks or bind EIPs to an existing spot pricing ECS, these resources must be manually released after the ECS is deleted.
If a node fails to be connected to the Internet, perform the following operations: Check Item 1: Whether an EIP Has Been Bound to the Node Log in to the ECS console and check whether an EIP has been bound to the ECS corresponding to the node.
production cluster resides) ECS In this example, there is one ECS located in vpc-X (with CIDR block of 192.168.0.0/16).
The number of extension network interfaces that you can attach to an ECS varies by ECS flavor. Parent Topic: Network Planning
An ECS in vpc-X (with CIDR block of 192.168.0.0/16) has been created. The recommended flavors for this ECS are 4 vCPUs and 16 GiB, and it runs Huawei Cloud EulerOS 2.0. An EIP has been bound to the ECS to pull images from the Internet.
The ECS system and data disks will be formatted while the ECS is being accepted into a cluster. Ensure that data in the disks has been backed up. During the acceptance of an ECS, do not perform any operation on the ECS through the ECS console.
Context After you change the flavor of a node in a CCE node pool on the ECS console and then synchronize the ECS status on the CCE console, the node flavor no longer matches the configurations in the node pool.