새 버전이 트래픽을 모두 수신할지, 일부만 수신할지, 전혀 수신하지 않을지 지정할 수 있고, 새 버전을 점진적으로 출시할 수 있고, 여러 버전 간에 트래픽을 분할할 수 있고, 버전에서 롤백할 수 있습니다. 자세한 내용은 롤백, 점진적 출시, 트래픽 마이그레이션을 참조하세요.
또한 Cloud Build 트리거를 사용하여 컨테이너를 빌드했으면 소스 저장소 정보도 세부정보 패널에 표시됩니다.
버전 삭제
일반적으로 특정 버전이 실수로 사용되지 않도록 하기 위해 버전을 삭제합니다.
다음 경우에는 버전을 삭제할 수 없습니다.
버전이 트래픽을 수신할 수 있는 경우
서비스의 유일한 버전일 경우
서비스의 최신 버전일 경우
버전을 삭제할 때 이 버전에 사용되는 컨테이너 이미지는 Container Registry 또는 Artifact Registry에서 자동으로 삭제되지 않습니다. 레지스트리에서 컨테이너 이미지를 삭제하려면 Container Registry 또는 Artifact Registry의 삭제 안내를 참조하세요.
[[["이해하기 쉬움","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-04(UTC)"],[],[],null,["# Managing revisions\n\nWhen you deploy to a service or change the configuration of a service, an\nimmutable revision is created.\n\nThe following considerations apply to revisions:\n\n- You can specify whether a new revision receives all, none, or some of the\n traffic, you can gradually roll out a new revision, you can split traffic\n between several revisions, and you can roll back from a revision. For more\n information, refer to\n [Rollbacks, gradual rollouts, and traffic migration](/kubernetes-engine/enterprise/knative-serving/docs/rollouts-rollbacks-traffic-migration).\n\n- You can optionally use [revision tags](/kubernetes-engine/enterprise/knative-serving/docs/rollouts-rollbacks-traffic-migration#tags)\n to test a revision that is not serving traffic.\n\n- You don't need to [manually delete revisions](#delete), although you can if you want.\n\n- Non-serving revisions do not consume any resources and are not billed.\n\n- There is a maximum of 1000 revisions per service: If you exceed that limit, older revisions are automatically deleted.\n\n- The revision suffix is assigned automatically. If you want to use your own\n version suffix, you can do so using the Google Cloud CLI parameter\n [--revision-suffix](/sdk/gcloud/reference/run/deploy#--revision-suffix).\n\nViewing the list of revisions for a service\n-------------------------------------------\n\n### Console\n\nTo view the list of revisions in your project:\n\n1. Go to Knative serving in the Google Cloud console:\n\n [Go to Knative serving](https://console.cloud.google.com/kubernetes/run)\n2. Locate the service in the services list, and click\n on it.\n\n3. Click the *Revisions* tab to show the list of current revisions for that\n service.\n\n### Command line\n\n\nTo view the list of revisions for a given service:\n\n1. Find your service name from the list of services available in your\n project:\n\n ```bash\n gcloud run services list\n ```\n2. List all the revisions for a service by specifying the name of that\n service in the following command:\n\n \u003cbr /\u003e\n\n ```bash\n gcloud run revisions list --service SERVICE\n ```\n\n \u003cbr /\u003e\n\n Replace \u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e with the name of your service.\n\nViewing revision details\n------------------------\n\n### Console\n\nTo view the details of a revision in your project:\n\n1. Go to Knative serving in the Google Cloud console:\n\n [Go to Knative serving](https://console.cloud.google.com/kubernetes/run)\n2. Locate the service in the services list, and click\n on it.\n\n3. Click the *Revisions* tab to show the list of current revisions for that\n service.\n\n4. Select the service revision you are interested in:\n\n5. Examine the *DETAILS* panel at the far right for revision-specific\n information such as the URL of the deployed container image, amount of\n memory allocated, environment variables, and possibly\n [build and source repository information](#build-source).\n\n### Command line\n\nTo view the details of a revision in your project:\n\n1. Find your service name from the list of services available in your\n project:\n\n \u003cbr /\u003e\n\n ```bash\n gcloud run services list\n ```\n\n \u003cbr /\u003e\n\n2. List all the revisions for a service by specifying the name of that\n service in the following command:\n\n \u003cbr /\u003e\n\n ```bash\n gcloud run revisions list --service SERVICE\n ```\n\n \u003cbr /\u003e\n\n Replace \u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e with the name of your service.\n3. Display details of a revision by specifying the name of that revision\n in the following command:\n\n \u003cbr /\u003e\n\n ```bash\n gcloud run revisions describe REVISION\n ```\n\n \u003cbr /\u003e\n\n Replace \u003cvar translate=\"no\"\u003eREVISION\u003c/var\u003e with the name of the revision you want to\n learn more about.\n | **Tip:** You can use the [`--format` flag](/sdk/gcloud/reference#--format) to format the output. For example as YAML:\n\n \u003cbr /\u003e\n\n ```bash\n gcloud run revisions describe REVISION --format yaml\n ```\n\n \u003cbr /\u003e\n\nNote that a non-current revision may have the status of `RETIRED`, which means\nthat Knative serving has retired the infrastructure needed for that\nparticular revision.\n\n### About build and source repository information in the *Details* panel\n\nIf the\n[Artifact Analysis API](/container-registry/docs/container-analysis)\nis enabled and the container was built with [Cloud Build](/build),\nbuild information is displayed in the *Details* panel.\n\nAdditionally, if a\n[Cloud Build trigger](/build/docs/running-builds/create-manage-triggers)\nwas used to build the container, source repository information is also displayed\nin the *Details* panel.\n\nDeleting revisions\n------------------\n\nA common use case for deleting a revision is when you want to make sure a\nparticular revision won't be accidentally used.\n\nYou cannot delete a revision if:\n\n- it is able to receive traffic,\n- it is the only revision of the service,\n- it is the latest revision of the service.\n\nWhen you delete a revision, the container image used by this revision is not\ndeleted automatically from Container Registry or Artifact Registry. To delete a\ncontainer image from a registry, see the deletion instructions for\n[Container Registry](/container-registry/docs/managing#deleting_images) or\n[Artifact Registry](/artifact-registry/docs/docker/manage-images#deleting_images).\n\nYou cannot undo a revision deletion.\n\nYou can use either the console or the command line: \n\n### Console\n\nTo delete a revision:\n\n1. Go to Knative serving in the Google Cloud console:\n\n [Go to Knative serving](https://console.cloud.google.com/kubernetes/run)\n2. Locate the service in the services list, and click\n on it.\n\n3. Click the *Revisions* tab to show the list of current revisions for that\n service.\n\n4. Locate the service revision you want to delete.\n\n5. Click the three-dot vertical ellipse to the left of the revision to show\n the *Delete* menu.\n\n6. Click **Delete** to delete the revision.\n\n### Command line\n\nTo delete a revision, use the following command:\n\n\u003cbr /\u003e\n\n```bash\ngcloud run revisions delete REVISION\n```\n\n\u003cbr /\u003e\n\nReplace \u003cvar translate=\"no\"\u003eREVISION\u003c/var\u003e with the name of the revision you want to delete.\n\nWhat's next\n-----------\n\nAfter you deploy a revision, you can do the following:\n\n- [Gradual rollouts, rollback revisions, traffic migration](/kubernetes-engine/enterprise/knative-serving/docs/rollouts-rollbacks-traffic-migration)"]]
