[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[[["\u003cp\u003eCloud Endpoints utilizes the Extensible Service Proxy (ESP) and Service Management to manage APIs, where deploying an OpenAPI document creates a managed service.\u003c/p\u003e\n"],["\u003cp\u003eDeleting an API involves removing both the instance running ESP and the API backend, as well as the managed service created for that API.\u003c/p\u003e\n"],["\u003cp\u003eInstances can be deleted using different methods based on the environment, such as disabling applications in App Engine or using \u003ccode\u003egcloud compute instances delete\u003c/code\u003e for Compute Engine and \u003ccode\u003egcloud container clusters delete\u003c/code\u003e for GKE.\u003c/p\u003e\n"],["\u003cp\u003eManaged services can be deleted via the gcloud CLI, but they are only disabled for 30 days initially, providing a window for potential restoration before permanent deletion.\u003c/p\u003e\n"],["\u003cp\u003eIf you do not require any data stored in the Endpoints Services or Produced API logs, you are able to delete the service.\u003c/p\u003e\n"]]],[],null,["# Deleting an API and API instances\n\nOpenAPI \\| [gRPC](/endpoints/docs/grpc/deleting-an-api-and-instances \"View this page for the Cloud Endpoints gRPC docs\")\n\n\u003cbr /\u003e\n\nCloud Endpoints uses the\n[Extensible Service Proxy (ESP)](/endpoints/docs/openapi/glossary#extensible_service_proxy)\nand Service Management to manage your API. When you deployed your\nOpenAPI document by using the `gcloud endpoints services deploy` command, the\ncommand used Service Management to create a managed service for your API.\n\nTo delete your API you need to:\n\n- Delete the instance that ESP and your API backend is running on.\n- Delete the managed service that was created for your API.\n\nThe easiest way to do both of these tasks is to delete the Google Cloud\nproject that your API is in. If you want to preserve your\nGoogle Cloud project, then you need to delete the instance and the managed\nservice.\n| **Note:** If you encounter issues with Google Cloud project deletion, refer to the [troubleshooting](/resource-manager/docs/troubleshooting-project-deletion) section for resolution.\n\nDeleting instances\n------------------\n\n### App Engine\n\nTo delete an instance running in the App Engine flexible environment:\n\nYou can either disable the application on the **App\nEngine Settings** page in the Google Cloud console, or\nyou can delete the Google Cloud project. See [Disabling\nan application and shutting down a project](https://cloud.google.com/appengine/docs/flexible/python/managing-projects-apps-billing#disabling_an_application) for more information.\n\n### Compute Engine\n\nUse the [`gcloud compute instances delete`](/sdk/gcloud/reference/compute/instances/delete)\ncommand. When you delete an instance in this way, the instance shuts down and\nis removed from the list of instances, and all resources attached to the\ninstance are released, such as persistent disks and any static IP addresses.\n\nTo delete an instance, use the following command: \n\n```transact-sql\ngcloud compute instances delete [INSTANCE_NAME] --zone = [ZONE]\n```\n\nFor more information on deleting Compute Engine instances, see the\n[Compute Engine documentation](/compute/docs/instances/stopping-or-deleting-an-instance).\n\n### GKE\n\nTo delete a GKE cluster with the Google Cloud CLI: \n\n```transact-sql\ngcloud container clusters delete [NAME] --zone [ZONE]\n```\n\nReplace `[NAME]` with the name of your cluster and\n`[ZONE]` with the compute zone that the cluster is in.\n\nFor more information on deleting a GKE cluster, see the\n[GKE documentation](/kubernetes-engine/docs/how-to/deleting-a-cluster).\n\nDeleting the managed service\n----------------------------\n\nIf you don't need the data on the **Endpoints Services** page and in the\n**Produced API** log on the **Logs Explorer** page, you can delete the managed\nservice for your API, which removes the data from the Google Cloud console.\n\nTo delete the managed service:\n\n1. Make sure that the gcloud CLI (`gcloud`) is authorized to access your\n data and services on Google Cloud:\n\n gcloud auth login\n\n2. Enter the following to display the project IDs for your Google Cloud\n projects:\n\n gcloud projects list\n\n3. Using the applicable project ID from the previous step, set the default\n Google Cloud project to the one that your application is in:\n\n gcloud config set project [YOUR_PROJECT_ID]\n\n4. Obtain the name of all managed services in your Google Cloud project:\n\n gcloud endpoints services list\n\n5. Delete the service from Service Management. Replace\n \u003cvar translate=\"no\"\u003eSERVICE_NAME\u003c/var\u003e with the name of the service you want\n to remove.\n\n ```\n gcloud endpoints services delete SERVICE_NAME\n ```\n\n Running `gcloud endpoints services delete` doesn't immediately delete the\n managed service. Service Management disables the managed service for\n 30 days, which allows you time to restore it if you need to. After 30 days,\n Service Management permanently deletes the managed service.\n\nWhat's next\n-----------\n\n- To restore a managed service, see\n [Restoring a managed service](/endpoints/docs/openapi/restore-managed-service).\n\n- For information on the `gcloud` commands used on this page, see the\n [gcloud reference](/sdk/gcloud/reference).\n\n- For information on Service Management, see\n [Creating and deleting managed services](/service-infrastructure/docs/create-services)."]]
