检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Once a VM name is altered on the ECS console, the node name cannot be modified accordingly during ECS synchronization. To prevent conflicts between Kubernetes node names, a suffix is automatically added to the node name of a node configured with cceNodeName.
However, when inventory runs low, or the market price rises and exceeds the highest price you are willing to pay, the system automatically reclaims your ECS instances at short notice.
Similarly, to enable cross-ECS pod access in a VPC, the CIDR block of the ECS where the target pod runs must be added.
For details, see How Do I Change the DNS Server Address of an ECS? For more details, see Version Differences. Version Differences Upgrade Path Version Difference Self-Check v1.23 or v1.25 Upgraded to v1.27 Docker is no longer recommended. Use containerd instead.
Default: none The CPU management policy does not apply to ECS (PM) node pools in CCE Turbo clusters. QPS for requests to kube-apiserver kube-api-qps Number of queries per second for communication with the API server.
Physical ECS nodes in a CCE Turbo cluster cannot be migrated. Calling Method For details, see Calling APIs.
v1.27.16-r10 or later v1.28: v1.28.15-r0 or later v1.29: v1.29.10-r0 or later v1.30: v1.30.6-r0 or later Other clusters of later versions Forward to a custom backend server group Forward LoadBalancer ingress requests to both pods in the CCE cluster (default backend server group) and an ECS
