检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
(Optional) Add the metadata associated with the cluster to ensure that the EVS disk associated with the mounted static PV is not deleted when the node or cluster is deleted.
If a listener added on the ELB console is used, manually delete this load balancer. Deleting a listener automatically added by CCE Accessing the target Service or ingress will fail.
After the webhooks.admissionReviewVersions fields of the objects in Table 1 are modified, delete the vcjob resource that fails to run properly. kubectl delete vcjob -n namespace vcjob_name Information similar to the following is displayed: vcjob vcjob_name deleted Recreate the vcjob
You need to manually delete these resources. After the PVC is deleted, the PV is in the Released state and cannot be bound to a PVC again. If you want to continue using the underlying storage resources, delete the PV first.
Locate the rows that contain the namespaces with the node-local-dns-injection=enabled label and delete the label. For details, see Managing Namespace Labels. Delete the pods in these namespaces and recreate pods.
You can also migrate services to other available nodes, create a node, and delete the faulty node to skip subsequent steps. Handle events. Go to the ECS console to check events and handle ECS events by event type. Perform post-processing.
docker images Delete the unnecessary images by image ID. docker rmi {}Image ID} Do not delete system images such as the cce-pause image.
None crictl stopp None Delete a pod.
fsType: nfs volumeID: f6976f9e-2493-419b-97ca-d7816008d91c persistentVolumeReclaimPolicy: Delete storageClassName: nfs-rw Table 1 Key parameters Parameter Description driver Storage driver used to mount the volume.
PersistentVolumeClaim name: pvc-obs-example namespace: default flexVolume: driver: huawei.com/fuxiobs fsType: obs options: fsType: obs region: ap-southeast-1 storage_class: STANDARD volumeID: test-obs persistentVolumeReclaimPolicy: Delete
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.
In the displayed dialog box, click Add Operation under Batch Operation, and then choose Add/Update or Delete as well as Taint. Enter the key and value of the taint to be operated, choose a taint effect, and click OK.
Options: retain-volume-only: When a PVC is deleted, the PV is deleted, but its associated subdirectories are retained. delete: When a PVC is deleted, the PV and its associated subdirectories are also deleted.
Delete the kernel.printk configuration. sed -i '/^kernel.printk/d' /etc/sysctl.conf Run the following command to check whether the configuration file is modified.
Stopping Billing If you no longer need to use your cloud service resources, you can unsubscribe from or delete them to stop the billing. For details, see Billing Termination.
Then, delete the grayscale released ingress.
Do not manually delete the corresponding storage pool or detach data disks from the node. Otherwise, exceptions such as data loss may occur. Ensure that the /var/lib/kubelet/pods/ directory is not mounted to the pod on the node.
EulerOS 2.10: polkit-0.116-6.h4 EulerOS 2.9: polkit-0.116-5.h7 EulerOS 2.8: polkit-0.115-2.h14 EulerOS 2.5: polkit-0.112-14.h15 If no patch is available in your system, run the # chmod 0755 /usr/bin/pkexec command to delete SUID-bit from pkexec.
following kubelet versions are affected by this vulnerability: kubelet v1.18.0 to v1.18.5 kubelet v1.17.0 to v1.17.8 kubelet < v1.16.13 Solution You are advised to take the following security measures: Set the cluster pod security policy or the admission mechanism to force pods to delete
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.
