[[["易于理解","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-08-04。"],[],[],null,["# Quickstart: Deploy an application to Knative serving\n\nDeploy an application to Knative serving\n========================================\n\nLearn how to use the Google Cloud console to deploy a prebuilt sample\ncontainer to run as a Knative serving service.\n\nBefore you begin\n----------------\n\nYou must have access to the Google Cloud project and cluster\nwhere Knative serving is installed. For details, see\n[Knative serving fleet installation overview](/kubernetes-engine/enterprise/knative-serving/docs/install).\n\n**Tip** : See the [GKE Enterprise tutorial](/anthos/docs/tutorials/explore-anthos)\nfor details about the shortest path to setting up a GKE Enterprise environment\nthat includes a GKE cluster and Cloud Service Mesh.\n\nDeploying a sample container\n----------------------------\n\nUse the Google Cloud console to deploy a sample container and create a service\nin your cluster:\n\n1. In the Google Cloud console, go to the **Knative serving** page.\n\n [Go to Knative serving](https://console.cloud.google.com/projectselector2/kubernetes/run)\n2. Select the Google Cloud project in which your GKE cluster resides.\n\n3. In the list of available clusters, click **Login** to connect.\n\n4. Open the **Create service** form by clicking **Create service**.\n\n5. In the available clusters dropdown menu, select your cluster.\n\n6. Leave `default` as the name of the\n [namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/)\n where you want your service to run.\n\n7. Enter a service name of your choice. For example, `hello`.\n\n8. Click **Next**.\n\n9. Select **Deploy one revision from an existing container image** , then\n select **hello** from in the **Demo containers** list.\n\n10. Click **Next**.\n\n11. Select **External** under *Connectivity*, so that you can access your\n service from the web.\n\n12. Click **Create** to deploy the `hello` image to Knative serving\n and wait for the deployment to finish.\n\nCongratulations! You have just deployed a service to a\nKnative serving enabled cluster.\n\nAccessing your deployed service\n-------------------------------\n\nNow that you have a service running, you can send requests to it. In this\nsection, assuming that your cluster uses default name of the ingress gateway,\nthe default test domain is used to demonstrate how to access your\nservice and verify that it's working:\n\n1. In the Google Cloud console, go to the **Knative serving** page.\n\n [Go to Knative serving](https://console.cloud.google.com/kubernetes/run)\n2. Click the name of your new Knative serving service to open the\n **Service details** page. For example, **hello**.\n\n3. At the top of the page, click the **URL** to access your deployed service\n through your web browser. For example, if you named your service `hello`, the\n URL is similar to the following but includes your cluster's external IP\n address: `http://hello.default.kuberun.11.111.11.111.nip.io`\n\nCongratulations! Your Knative serving service is live and handling requests.\n\nClean up\n--------\n\nYou can delete the Knative serving service to avoid incurring costs from\nrunning those resources.\n\nThe following considerations apply to deleting a service:\n\n- Deleting a service deletes all resources related to this service, including all revisions of this service whether they are serving traffic or not.\n- Deleting a service does not automatically remove container images from Container Registry.\n To delete container images used by the deleted revisions from Container Registry,\n refer to [Deleting images](/container-registry/docs/managing#deleting_images).\n\n | **Caution:** Container Registry is deprecated. Effective March 18, 2025,\n | Container Registry is shut down, and writing images to Container Registry is unavailable. For\n | details on the deprecation and how to migrate to Artifact Registry, see\n | [Container Registry deprecation](/container-registry/docs/deprecations/container-registry-deprecation).\n- Deleting a service with one or more Eventarc triggers does not automatically\n delete these triggers. To delete the triggers refer to [Manage triggers](/eventarc/docs/managing-triggers#trigger-delete).\n\n- After deletion, the service remains visible in the Google Cloud console and in the command line interface\n until the deletion is fully complete. However, you cannot update the service.\n\n- Deleting a service is permanent: there is no undo or restore.\n However, if after deleting a service, you deploy a new service with the same\n name in the same region, it will have the same endpoint URL.\n\nTo permanently delete the service and all its resources:\n\n1. In the Google Cloud console, go to the **Knative serving** page.\n\n [Go to Knative serving](https://console.cloud.google.com/kubernetes/run)\n2. In the services list, locate the Knative serving service that you created\n and click its checkbox to select it.\n\n3. Click **DELETE**.\n\nWhat's next\n-----------\n\nTo learn how to build a container from code source, push to Container Registry,\nand then deploy, see:\n\n- [Building containers](/kubernetes-engine/enterprise/knative-serving/docs/building/containers)\n- [Deploying container images](/kubernetes-engine/enterprise/knative-serving/docs/deploying)\n\nTo learn more about how Knative serving works, see the\n[Architectural overview](/kubernetes-engine/enterprise/knative-serving/docs/architecture-overview)."]]