检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
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.
If the reclamation policy of a general purpose file system (SFS 3.0 Capacity-Oriented) is set to Delete, PVs and PVCs can be properly deleted only after all files are manually deleted from the mounted file system.
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.
Obtain pods, shown as below: $ kubectl get pods NAME READY STATUS RESTARTS AGE nginx-7f98958cdf-tdmqk 1/1 Running 0 13s nginx-7f98958cdf-txckx 1/1 Running 0 13s If you delete a pod, a new pod is immediately created
command: - ls - /ready imagePullSecrets: - name: default-secret Save the above Deployment definition in the deploy-ready.yaml file, delete the existing Deployment, and use the deploy-ready.yaml file to recreate the Deployment. # kubectl delete deploy
the TFJob. kubectl delete -f tf-mnist.yaml Using a GPU The training can be performed in the GPU scenario.
To remove the configuration, use kubernetes.io/elb.cors-disabled to delete all cross-origin settings. kubernetes.io/elb.cors-allow-credentials: 'true' kubernetes.io/elb.cors-max-age String Specify Access-Control-Max-Age for the cache duration of a CORS pre-check request.
Run the following command to delete the pod named web-demo-846b489584-mjhm9: kubectl delete pod web-demo-846b489584-mjhm9 Expected output: pod "web-demo-846b489584-mjhm9" deleted After the deletion, the Deployment controller automatically creates a replica.
When updating a StatefulSet in Kubernetes, it is not allowed to add or delete the volumeClaimTemplates field. This field can only be configured during the creation of the StatefulSet.
This mode is suitable for flexible scenarios where you may need to provision or delete resources at any time. For more details, see Billing Modes. Cluster Name cce-test Enter a name for the cluster.
After a slow start is configured, if you delete the target annotation from the YAML file, slow start will not be enabled. Prerequisites A CCE standard or Turbo cluster is available, and the cluster version is v1.23 or later.
After a slow start is configured, if you delete the target annotation from the YAML file, slow start will not be enabled. Prerequisites A CCE standard or Turbo cluster is available, and the cluster version is v1.23 or later.
Delete the pods based on the node IP address to restart the huawei-npu-device-plugin component 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.
When updating a StatefulSet in Kubernetes, it is not allowed to add or delete the volumeClaimTemplates field. This field can only be configured during the creation of the StatefulSet.
However, when this method is used to add or delete a node, all IP addresses need to be hashed again and then routed again. As a result, a large number of sessions are lost or the cache becomes invalid.
To minimize risks, delete the configuration and redeploy the container. In a running container, if WORKDIR in the used image is set to /proc/self/fd/<num>, this vulnerability still exists. To minimize risks, use a trusted image and redeploy the container.
Mount directory configuration everest.io/share-source: sfs-turbo everest.io/share-volume-type: STANDARD everest.io/volume-as: subpath everest.io/volume-id: 0d773f2e-1234-1234-1234-de6a35074696 # ID of an SFS Turbo volume provisioner: everest-csi-provisioner reclaimPolicy: Delete
Mount directory configuration everest.io/share-source: sfs-turbo everest.io/share-volume-type: STANDARD everest.io/volume-as: subpath everest.io/volume-id: 0d773f2e-1234-1234-1234-de6a35074696 # ID of an SFS Turbo volume provisioner: everest-csi-provisioner reclaimPolicy: Delete
CCE will automatically delete the labels for the cluster ID, namespace, and pod name that were added when the EIP was bound.