[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-01 (世界標準時間)。"],[],[],null,["# Resource model\n\nThe following diagram shows the Knative serving resource model:\n\nThe diagram shows a Google Cloud project containing two Knative serving\nservices, `Service A` and `Service B`, each of which has several revisions.\n\nIn the diagram, `Service A` is receiving many requests, which results in the\nstartup and running of several container instances. Note that `Service B` is\nnot currently receiving requests, so no container instance is started yet.\n\nKnative serving services\n------------------------\n\nThe service is the main resource of Knative serving.\nEach service is located in a specific [GKE cluster namespace](/blog/products/gcp/kubernetes-best-practices-organizing-with-namespaces).\n\nA given Google Cloud project can run many services in different regions or\nGKE clusters.\n\nEach service exposes a unique endpoint and automatically scales the underlying\ninfrastructure to handle incoming requests.\n\nKnative serving revisions\n-------------------------\n\nEach deployment to a service creates a revision. A revision consists of a\nspecific container image, along with environment settings such as environment\nvariables, memory limits, or concurrency value.\n\nRevisions are immutable: once a revision has been created, it cannot be\nmodified. For example, when you deploy a container image to a new\nKnative serving service, the first revision is created. If you then deploy a\ndifferent container image to that same service, a second revision is created. If\nyou subsequently set an environment variable, a third revision is created, and so\non.\n\nRequests are automatically routed as soon as possible to the latest healthy\nservice revision. You can\n[split traffic](/kubernetes-engine/enterprise/knative-serving/docs/rollouts-rollbacks-traffic-migration#split-traffic)\nbetween different revisions as desired.\n\nKnative serving container instances\n-----------------------------------\n\nEach revision receiving requests is automatically scaled to the number of\ncontainer instances needed to handle all these requests. Note that a container\ninstance can receive many requests at the same time. With the\n[concurrency setting](/kubernetes-engine/enterprise/knative-serving/docs/configuring/concurrency), you can set the\nmaximum number of requests that can be sent in parallel to a given container\ninstance."]]