检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
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.
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.
If the cluster is no longer needed, you can delete it and other cloud service resources in the cluster to avoid further expenditures. If your account is in arrears, top up your account in time.
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.
After the function of obtaining the client IP address is enabled, if you delete the target annotation from the YAML file, the configuration on the ELB will be retained.
Delete the faulty node and upgrade the cluster again. Parent Topic: Troubleshooting for Pre-upgrade Check Exceptions
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.
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.
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.
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.
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.
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.
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.
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.
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.
To uninstall the add-on, run the following kubectl command and delete the APIService object.
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.
