检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
If - name: overcommit exists, delete this configuration. ... data: volcano-scheduler.conf: | actions: "allocate, backfill, preempt" # Configure a preemption action.
Download the kubeconfig files of the two clusters and delete the lines related to private network access, as shown in the following figure.
$ kubectl delete po nginx-869759589d-dnknn pod "nginx-869759589d-dnknn" deleted $ kubectl get po -o wide NAME READY STATUS RESTARTS AGE IP NODE nginx-869759589d-fcxhh 1/1 Running 0 5h41m 172.16.3.6 192.168.0.212
You can create, modify, and delete monitoring tasks in the preceding format. A maximum of 10 monitoring tasks can be created.
You can manually delete the release and reinstall it. status_description String Release status description update_at String Update time. values String Release value version Integer Release version Example Requests POST /cce/cam/v3/clusters/{cluster_id}/releases { "name" : "nino21
You can manually delete the release and reinstall it. status_description String Release status description update_at String Update time. values String Release value version Integer Release version Example Requests PUT /cce/cam/v3/clusters/{cluster_id}/namespace/{namespace}/releases
Public Read/Write: Anyone can read, write, or delete objects in the bucket. Replicate Bucket Policy: The policy of the selected source bucket will be applied to the bucket you are creating. This option is only available if you have selected a bucket as the replication source.
To remove the configuration, use kubernetes.io/elb.cors-disabled to delete all cross-origin settings. kubernetes.io/elb.cors-max-age String Specify Access-Control-Max-Age for the cache duration of a CORS pre-check request. Unit: second.
If you have deleted a label or taint in the node pool, you must manually delete the label or taint on the node list page after Kubernetes labels or Taints is selected.
If you have modified the add-on startup parameters, check and delete the custom parameters before the rollback. If you do not perform these operations, the rollback may fail because the target version does not support these parameters.
After the CCE Cluster Autoscaler add-on is uninstalled, if the taint still exists on the node, manually delete it. To ensure system stability and efficient resource utilization, CCE Cluster Autoscaler uses a conservative policy.
To remove a node from a node pool, do not delete the node directly. Instead, adjust the number of nodes in the node pool. For details, see Scaling a Node Pool. If your node pool malfunctions, locate the fault by referring to What Should I Do If a Node Pool Is Abnormal?
If you stop, restart, or delete nodes while upgrading the cluster, the upgrade will fail. Before upgrading a cluster, ensure no high-risk operations are performed in the cluster. Otherwise, the cluster upgrade may fail or the configuration may be lost after the upgrade.
Do not manually modify or delete the load balancer and listener that are automatically created by CCE. Otherwise, the workload will be abnormal. If you have modified or deleted them by mistake, uninstall the nginx-ingress add-on and re-install it.
If multiple lines are not required, delete processors. type: multiline # Log type, which is optional. The value can be singleline or multiline. The default value is singleline. multilineRegulation: '\d+:\d+:\d+.*?' # Multi-line regular expression, which is optional.
Can Data Be Restored If Underlying EVS Disks Are Deleted or Expired? If underlying EVS disks are deleted, you may encounter the following situations: If you have created snapshots for the PVCs, you can restore data using the snapshots. For details, see Using a Snapshot to Create a
How Do I Retrieve Data After a CCE Cluster Is Deleted? Question How do I retrieve data after a CCE cluster is deleted? Answer After a cluster is deleted, the workload on the cluster will also be deleted and cannot be restored. Therefore, exercise caution when deleting a cluster. Parent
Why Is the Backend Server Group of an ELB Automatically Deleted After a Service Is Published to the ELB? Symptom After a Service is published to ELB, the workload is normal, but the pod port of the Service is not published in time. As a result, the backend server group of the ELB
You can manually delete the cluster. jobID String Details: ID of the job associated with the current cluster status. It supports: ID of the associated job returned during cluster creation. You can use it to obtain the auxiliary job information for creating a cluster.
You can manually delete the cluster. jobID String Details: ID of the job associated with the current cluster status. It supports: ID of the associated job returned during cluster creation. You can use it to obtain the auxiliary job information for creating a cluster.
