检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Users granted these permissions can create, delete, query, and update all CCI 2.0 resources. Perform the federated identity authentication as the delegated party. Log in to as the delegated party (account B) and perform federated identity authentication.
To uninstall the add-on, run the following kubectl command and delete the APIService object first or the add-on cannot be installed due to residual APIService resources. kubectl delete APIService v1beta1.metrics.k8s.io Create an HPA policy. Log in to the CCE console.
set-credentials cluster-admin --client-certificate=~/.kubev2/admin.crt --embed-certs=true # Enable the IAM identity authentication provider for the cluster-admin entry. ccictl config set-credentials cluster-admin --auth-provider=iam --auth-provider-arg=iam-endpoint=example.com # Delete
Stopping Billing If you no longer need to use your cloud service, you can unsubscribe from or delete it to stop the billing. For details, see Stopping Billing.
Figure 1 Lifecycle of a pay-per-use pod Avoiding and Handling Arrears If the data stored in CCI is no longer used, you can delete it to avoid additional cost.
If a CCI 2.0 namespace has been created in a shared VPC, the owner of the shared VPC cannot delete the resource share, or the namespace will work abnormally.
"false" or "ignore" will not perform any schema definition checks, but will silently delete all unknown or duplicate fields. --windows-line-endings The default value is the native line ending format of your platform.
"false" or "ignore" will not perform any schema definition checks, but will silently delete all unknown or duplicate fields. --windows-line-endings This option is related only when --edit is set to true. The default value is the native line end format of your platform.
"false" or "ignore" will not perform any schema definition checks, but will silently delete all unknown or duplicate fields. --windows-line-endings The default value is the native line end format of your platform.
Deleting a Pod You can manually delete pods. Because pods are controlled by a controller, a new pod will be created immediately after you delete a pod. Manual pod deletion is useful when an upgrade fails halfway or when service processes need to be restarted.
You need to periodically review and delete expired image snapshots. .spec.imageSnapshotSize integer No 20 Image snapshot size, in GiB. The default value is 20. Parent topic: Image Snapshots
"false" or "ignore" will not perform any schema definition checks, but will silently delete all unknown or duplicate fields. --wait If the value is true, the resource is returned after it disappears. This waits for the finalizer.
You can also delete pods if you no longer need them. Prerequisites A namespace has been created. If there are no namespaces, create one by referring to Creating a Namespace. The image has been uploaded. For details, see Pushing an Image Through a Container Engine Client.
Do not delete them. To change the retention period, go to the LTS console, select the log group from the log group list, and click Modify in the Operation column.
Edit the config file and delete sensitive information. In a Linux OS, the config file is stored in $HOME/.kubev2/config by default.
If there are multiple networks in a namespace, you can delete the default network configuration. However, you need to reconfigure a new default network after the deletion. Otherwise, the network function is abnormal.
Deleting a tag: Click Delete in the Operation column of the tag. WARNING: Deleted tags cannot be recovered. If a tag is used by a transfer task, you need to modify the task configuration after deleting the tag. Remark Enter remarks. The value contains up to 1,024 characters.
