检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
To delete a single threshold, click Delete in the Operation column of the threshold rule list. To delete threshold rules in bathes, select one or more threshold rules and click Delete on the upper part of the page. In the displayed dialog box, click OK.
Delete the extra instances you no longer use. For details, see Deleting a Component. Pause the extra instances you no longer use. For details, see Starting and Stopping a Component Instance. Professional Delete the instances you no longer use.
Deleting a Configuration Delete a configuration. Deleting All Configurations Delete all configurations.
Unbinding a CCE cluster from the environment will not delete the cluster instances. To delete them, see Deleting a Cluster. Parent topic: Managing CCE Resources
Deleting an image repository Click Delete in the upper-right corner of the page and delete the image repository as prompted. Deleting an image tag In the Operation column of the target image tag, click Delete to delete the image tag as prompted.
All: Add, delete, modify, and query resources in the service group and configuration group. Add: Add resources to the service group and configuration group. Delete: Delete resources from the service group and configuration group.
Delete the microservice of the service to completely uninstall the service. To delete a resource, obtain the corresponding permissions. If a message is displayed indicating that you do not have the permissions, apply for the permissions by referring to ServiceStage Permissions.
Do not delete or modify the directory. Otherwise, the installed VM agent may be offline. /var/log/application: directory for storing component logs. Do not delete or modify the directory. Otherwise, the installed VM agent may be offline.
Take the instance offline and then delete the microservice. Alternatively, forcibly delete the microservice by setting the query parameter force to true in the URL. 400014 Bad Request The schema ID does not exist.
Delete all components of the application and then delete the application. 409 SVCSTG.00100413 Conflict The instance name already exists. Use another instance name. 409 SVCSTG.00100419 Conflict The operation cannot be performed in the current state.
Deleting a configuration item Click Delete in the Operation column of the target configuration item. In the displayed dialog box, click OK. Deleting configuration items in batches Select the configuration items to be deleted. Click Delete Configuration Item.
], "Effect": "Allow" }, { "Action": [ "cse:engine:create", "cse:engine:delete" ], "Effect
DELETE https://{endpoint}/v4/{project_id}/registry/microservices/{service_id}/instances/{instance_id} Example Response None Status Code Status Code Description 200 OK 400 Bad Request 500 Internal Server Error Error Code See ServiceComb Error Codes.
resources but not permission to delete them.
Deleting a secret Click Delete in the Operation column of the target secret. In the displayed dialog box, click OK. Deleting secrets in batches Select the secrets to be deleted. Click Delete Key. In the displayed dialog box, click OK.
In the Backup and Restoration area, click Delete in the Operation column of the target backup data. In the displayed dialog box, enter DELETE and click OK. Parent topic: Managing Microservice Engines
In this case, you need to delete the components, create them again, and then deploy them. ServiceStage release management can be used to migrate and upgrade components across AZs. Batch clone release tasks can be used to migrate components across AZs.
Operation Description Restart a single instance If an instance of a component deployed in the Kubernetes environment is abnormal, you can delete the instance to restart it. Select the instance to be deleted and click Delete in the Operation column.
Delete the deployed microservice application component instances. Choose Application Management. Click the application where the microservice application is located. The Overview page is displayed.
DELETE: requests the server to delete specified resources, for example, an object. HEAD: requests a server resource header. PATCH: requests the server to update partial content of a specified resource. If the resource does not exist, a new resource will be created.