检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Do not manually delete the corresponding storage pool or detach data disks from the node. Otherwise, exceptions such as data loss may occur. Local PVs are in non-shared mode and cannot be mounted to multiple workloads or tasks concurrently.
However, if the existing EIP was manually created, it will be unbound from the load balancer when you delete the ingress, 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.
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.
However, if the existing EIP was manually created, it will be unbound from the load balancer when you delete the ingress, 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.
If you delete a Helm v2 release in the background, the release information is still displayed on the charts page on the CCE console. In this case, delete it. Installing Helm v2 This section uses Helm v2.17.0 as an example.
If the CCE Container Storage (Everest) version is earlier than 2.4.105 or the target region is CN South-Guangzhou, and the Delete reclaim policy is used for the general purpose file system (SFS 3.0 Capacity-Oriented), you must delete files from the file system.
After the cluster is upgraded, delete the existing pods to trigger pod rebuilding. Then, the access to sock will be recovered. Scenario 3: This issue occurred on some CCE add-ons of earlier versions. Upgrade the CCE add-ons to the latest version.
Do not delete it, as doing so will result in the failure of creating a node or load balancer. default-token-xxxxx By default, Kubernetes creates a service account named default for each namespace. default-token-xxxxx is the key of the service account, and xxxxx is a random number.
Do not delete it, as doing so will result in the failure of creating a node or load balancer. default-token-xxxxx By default, Kubernetes creates a service account named default for each namespace. default-token-xxxxx is the key of the service account, and xxxxx is a random number.
After the cluster is upgraded, delete the existing pods to trigger pod rebuilding. Then, the access to sock will be recovered. Scenario 3: This issue occurred on some CCE add-ons of earlier versions. Upgrade the CCE add-ons to the latest version.
After data compression is configured, if you delete the data compression configuration on the CCE console or delete the target annotation from the YAML file, the configuration on the ELB will be retained.
To avoid any additional expenditures, delete the ECS and all its resources. For details, see Billing for a Stopped ECS. After a common ECS is stopped, basic resources (vCPUs, memory, image, and GPUs) will not be billed.
Operation: Click Delete to delete the configuration. Annotation: The value is in the format of key-value pairs. You can use annotations to obtain the configurations supported by Nginx ingresses. Click OK. After the ingress is created, it is displayed in the ingress list.
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, HTTP/2 will be disabled on the ELB.
To collect all ServiceMonitor kubelet metrics, delete the metricRelabelings content (highlighted in red in the following figure). If you need to expand the kubelet metrics, edit the kubelet metrics. Extend kube-state-metrics metrics.
In this case, delete the workload, release the fixed IP address, and create a workload again. Before deleting a custom container network configuration, delete the pods (with the cni.yangtse.io/network-status annotation) created using the configuration in the target namespace.
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.
