检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
For example, if you connect a cluster to UCS at 08:45:30 and delete it at 08:55:30, you are billed for the 600 seconds from 8:45:30 to 8:55:30. Parent topic: Billing Modes
To avoid unexpected expenditures, go to the CCE console and manually delete the PVCs. (You need to uninstall the kube-prometheus-stack add-on first.) Procedure Select a fleet or a cluster that is not added to the fleet.
Deleting a ConfigMap Click Delete in the row where the target ConfigMap resides, and click Yes. Deleting ConfigMaps in batches Select the ConfigMap to be deleted. Click Delete in the upper left corner. Click Yes. Parent topic: ConfigMaps and Secrets
Stopping Billing If you no longer need to use your cloud services, you can unsubscribe from or delete them to stop the billing. For details, see Billing Termination.
After rectifying network faults, delete the existing proxy-agent pods and rebuild pods.
For example, if you delete a cluster (which is billed on an hourly basis) at 08:30, the expenditures for the hour from 08:00 to 09:00 are usually not billed until about 10:00.
After the cluster is successfully upgraded, delete the Remedy object. The traffic is automatically routed back to member1. In this way, the upgrade of a cluster will not affect the availability of services.
rbac.authorization.kubernetes.io/autoupdate: "true" creationTimestamp: null labels: kubernetes.io/bootstrapping: rbac-defaults rbac.authorization.k8s.io/aggregate-to-edit: "true" name: system:aggregate-to-edit rules: - apiGroups: - apps resources: - endpoints verbs: - create - delete
You can modify or delete the Services and ingresses automatically created by UCS on the cluster console. However, if the Service or ingress settings on the UCS console are not modified accordingly, the modified or deleted Services or ingresses will be re-created by UCS.
You can run the following command to obtain it: cat /var/paas/srv/kubernetes/kubeconfig | grep server If you need to update the certificate again, delete the files in the certificate directory and run the following command to update the certificate: rm -rf /var/paas/ucs/{cluster_name
Deleting a Service Choose More > Delete in the row where the target Service resides, and click Yes. Deleting Services in batches Select the Services to be deleted. Click Delete in the upper left corner. Click Yes. Parent topic: Services
Deleting an ingress Choose More > Delete in the row where the target ingress resides. Then, click Yes. Deleting ingresses in batches Select the ingresses to be deleted. Click Delete in the upper left corner. Click Yes. Parent topic: Services and Ingresses
If the certificate expires, download the kubeconfig file again and delete the temporary file. rm -f tls.crt Parent topic: Cluster Federation
Therefore, do not delete or modify the ucs_admin_trust agency when using UCS. If a misoperation is performed, see How Do I Restore System Agency ucs_admin_trust I Deleted?.
You can modify or delete the PVCs automatically created by UCS on the cluster console. However, if the PVC settings on the UCS console are not modified accordingly, the modified or deleted PVCs will be re-created by UCS. You are advised to change the settings on the UCS console.
Locate the request authentication policy to be deleted and click Delete in the Operation column. In the dialog box displayed, click Yes.
Delete: Delete the pod. View/Edit YAML: View or edit the YAML file of the workload. Delete: Delete the workload. Stop (for cron jobs only): Stop a cron job. Parent topic: Workload Management
Locate the authorization policy to be deleted and click Delete in the Operation column. In the dialog box displayed, click Yes.
Deleting a Service Choose More > Delete in the row where the target Service resides, and click Yes. Deleting Services in batches Select the Services to be deleted. Click Delete in the upper left corner. Click Yes. Parent topic: Services
In this case, do not delete the permissions. Otherwise, the authentication fails. You are advised to grant the cluster-admin permissions to a user group on UCS and add federated users to the user group.
