检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
After timeout is configured, if you delete the timeout configuration on the CCE console or delete the target annotation from the YAML file, the configuration on the ELB will be retained.
If you want to delete the risky node and purchase a new one, see Deleting a Node and Buying a Node. Parent Topic: Network Exception Troubleshooting
192.168.0.160 192.168.0.160 <none> <none> Evict all pods on the node. kubectl drain 192.168.0.160 If a pod mounted with local storage or controlled by a DaemonSet exists on the node, the message "eerror: unable to drain node "192.168.0.160" due to error: cannot delete
Log in to the CCE node (ECS) and delete the cpu_manager_state file. Example command for deleting the file: rm -rf /mnt/paas/kubernetes/kubelet/cpu_manager_state Restart the node or kubelet.
Do not delete or reset nodes during batch synchronization. Otherwise, the synchronization of node pool configuration may fail. This operation involves resetting nodes.
To resolve this issue, do as follows: Delete the NPU or vNPU workloads on the node, and then delete the ascend-vnpu-manager pod. NPU virtualization will function correctly on the node after the pod is restarted and runs properly.
the pod named web-local-auto-0: kubectl delete pod statefulset-local-0 Expected output: pod "statefulset-local-0" deleted After the deletion, the StatefulSet controller automatically creates a replica with the same name.
After HTTP or HTTPS is configured, if you delete the HTTP or HTTPS configuration on the CCE console or delete the target annotation from the YAML file, the configuration on the ELB will be retained.
Notes and Constraints After a blocklist or trustlist access policy is configured, if you delete the blocklist or trustlist access policy configuration on the CCE console or delete the target annotation from the YAML file, the configuration on the ELB will be retained.
You are advised to delete unnecessary ResourceQuota objects and configure resource quotas using the console. Procedure Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, click Namespaces.
Deleting a Cluster Delete an unused cluster to release resources. Yearly/Monthly Renewing a Yearly/Monthly Cluster Renew a yearly/monthly cluster before it expires. Unsubscribing From or Releasing a Yearly/Monthly Cluster A yearly/monthly cluster cannot be directly deleted.
Figure 1 Adding a pod subnet Add or delete the default pod subnet. You can select one or more subnets in the same VPC. If no other pod subnet is available, go to the VPC console and create one.
Deleting a Backup You can delete the backup objects and related objects (such as backups, restorations, and schedules) from a cluster and delete backups from the storage location when a large amount of backup data is generated.
To uninstall the add-on, run the following kubectl command and delete the APIService object.
the pod named web-local-0: kubectl delete pod web-local-0 Expected output: pod "web-local-0" deleted After the deletion, the StatefulSet controller automatically creates a replica with the same name.
However, if the existing EIP was manually created, it will be unbound from the load balancer when you delete the Service, and you will need to manually delete the EIP. Using kubectl Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
Before resetting a cluster for an upgrade, delete spot price nodes and set the number of pods in the spot price node pool to 0. If the quoted price is lower than the market price or if there are not enough resources available, spot price ECSs may be released.
After HTTP or HTTPS is configured, if you delete the HTTP or HTTPS configuration on the CCE console or delete the target annotation from the YAML file, the configuration on the ELB will be retained.
After HTTP/2 is configured, if you delete the advanced configuration for enabling HTTP/2 on the CCE console or delete the target annotation from the YAML file, the configuration on the ELB will be retained.
However, if the existing EIP was manually created, it will be unbound from the load balancer when you delete the Service, and you will need to manually delete the EIP. Using kubectl Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
