检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Run the kubectl delete -f high-priority-job.yaml command to release cluster resources and check pod scheduling.
BUCKET/PREFIX PHASE LAST VALIDATED ACCESS MODE DEFAULT default *** velero Available 2025-06-04 17:40:55 +0800 CST ReadWrite true Uninstalling Velero To completely uninstall Velero from a cluster, run the following command to delete
However, if a node becomes unavailable due to being deleted from the default node pool using kubectl delete node, it is excluded from the resource totals. This deletion method is not officially supported by CCE.
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.
In this case, delete the square bracket ([]). The following are the two parameters to be added: ... operatorConfigOverride: - lightweight.agent.max-block-size=31457280 - lightweight.agent.max-rows-per-block=30000 ... Click OK. Parent Topic: O&M Best Practices
the unnecessary images by image ID. crictl rmi {Image ID} Nodes that use Docker Obtain local images on the node. docker images Delete the unnecessary images by image ID. docker rmi {}Image ID} Do not delete system images such as the cce-pause image.
the pod named web-dss-auto-0: kubectl delete pod web-dss-auto-0 Expected output: pod "web-dss-auto-0" deleted After the deletion, the StatefulSet controller automatically creates a replica with the same name.
However, they do not allow granular permission configuration (create, delete, modify, and get) for specific resource types, such as pods, Deployments, or Services, within that namespace. Solution Kubernetes RBAC enables you to easily control permissions on namespace resources.
Redeploy the custom-metrics-apiserver workload in the monitoring namespace. kubectl -nmonitoring delete pod -l app=custom-metrics-apiserver Run the following command to check whether the metric is added: kubectl get --raw /apis/custom.metrics.k8s.io/v1beta1/namespaces/default/pods
Run the following command to delete the pod named web-demo-846b489584-mjhm9: kubectl delete pod -n <namespace> web-demo-846b489584-mjhm9 Expected output: pod "web-demo-846b489584-mjhm9" deleted After the deletion, the Deployment controller automatically creates a replica.
Run the rmmod xgpu_km command to delete GPU virtualization. Delete nvidia-gpu-device-plugin pods from the target node using the CCE console or kubectl command. After the nvidia-gpu-device-plugin pods are rebuilt, perform steps 2 and 3 again to verify the result.
Example 1: Configuring Write/Remove Header for a LoadBalancer Ingress You can modify or delete the headers specified in requests.
obs.csi.everest.io fsType: obsfs volumeAttributes: everest.io/obs-volume-type: STANDARD everest.io/region: ap-southeast-1 storage.kubernetes.io/csiProvisionerIdentity: everest-csi-provisioner volumeHandle: obs-normal-static-pv persistentVolumeReclaimPolicy: Delete
RWX csi-nas 29s $ kubectl get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE pvc-1f1c1812-f85f-41a6-a3b4-785d21063ff3 10Gi RWO Delete
It supports query, creation, update, and deletion of various cluster resources using standard HTTP request methods (POST, PUT, PATCH, DELETE, and GET). CCE allows you to use native Kubernetes APIs in the following ways: Calling Kubernetes APIs Through the Cluster API Server.
v1 kind: StorageClass metadata: name: csi-sfs-mount-option provisioner: everest-csi-provisioner parameters: csi.storage.k8s.io/csi-driver-name: nas.csi.everest.io csi.storage.k8s.io/fstype: nfs everest.io/share-access-to: <your_vpc_id> # VPC ID of the cluster reclaimPolicy: Delete
With dataset CRDs, you can create, update, delete, and monitor datasets in Kubernetes for efficient data management. Runtime CRD Manages the lifecycle of the underlying cache engine, including creation, scaling, and preloading, and supports multiple distributed cache systems.
Notes and Constraints If you delete the timeout configuration when updating an ingress, the timeout configuration of the existing listener will be retained.
Delete the rules and reconfigure them. After a Service is created, if the affinity setting is switched from the cluster level to the node level, the connection tracing table will not be cleared. Do not modify the Service affinity setting after the Service is created.
Components Table 4 Add-on components Component Description Resource Type everest-csi-controller Used to create, delete, snapshot, expand, attach, and detach storage volumes.
