检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
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 None Example Responses Status code: 200 OK [ { "chart_name" : "magento-mysql
In Kubernetes 1.5, the --prune flag was introduced in kubectl apply to delete resources that are no longer needed. This allowed kubectl apply to automatically clear resources removed from the current configuration.
Deleting a job Select the target job and choose More > Delete in the Operation column. Click Yes. Deleted jobs cannot be restored. Exercise caution when deleting a job. Parent Topic: Creating a Workload
Do not modify or delete the local disk. For details, see Configuring Time Zone Synchronization. Configure container settings for the workload. Container Information: Click Add Container on the right to configure multiple containers for the pod.
Delete unnecessary files to release disk space. If a dynamic volume is used, ensure that the storage backend configuration is correct and available. Expand the disk capacity or adjust the storage requirements of applications or services as needed.
In Kubernetes 1.5, the --prune flag was introduced in kubectl apply to delete resources that are no longer needed. This allowed kubectl apply to automatically clear resources removed from the current configuration.
After obtaining the images.json file, you can modify, add, or delete its content as needed. How to Use image-migrator image-migrator can run on Linux (x86 and Arm) and Windows. The usage is similar in both environments.
If - name: overcommit exists, delete this configuration. ... data: volcano-scheduler.conf: | actions: "allocate, backfill, preempt" # Configure a preemption action.
$ 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
Download the kubeconfig files of the two clusters and delete the lines related to private network access, as shown in the following figure.
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.
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 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.
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.