Stay organized with collections
Save and categorize content based on your preferences.
When you deploy to a service or change the configuration of a service, an
immutable revision is created.
The following considerations apply to revisions:
You can specify whether a new revision receives all, none, or some of the
traffic, you can gradually roll out a new revision, you can split traffic
between several revisions, and you can roll back from a revision. For more
information, refer to
Rollbacks, gradual rollouts, and traffic migration.
You can optionally use revision tags
to test a revision that is not serving traffic.
Non-serving revisions do not consume any resources and are not billed.
There is a maximum of 1000 revisions per service: If you exceed that limit, older revisions are automatically deleted.
The revision suffix is assigned automatically. If you want to use your own
version suffix, you can do so using the Google Cloud CLI parameter
--revision-suffix.
Viewing the list of revisions for a service
Console
To view the list of revisions in your project:
Go to Knative serving in the Google Cloud console:
Locate the service in the services list, and click
on it.
Click the Revisions tab to show the list of current revisions for that
service.
Select the service revision you are interested in:
Examine the DETAILS panel at the far right for revision-specific
information such as the URL of the deployed container image, amount of
memory allocated, environment variables, and possibly
build and source repository information.
Command line
To view the details of a revision in your project:
Find your service name from the list of services available in your
project:
gcloudrunserviceslist
List all the revisions for a service by specifying the name of that
service in the following command:
gcloudrunrevisionslist--serviceSERVICE
Replace SERVICE with the name of your service.
Display details of a revision by specifying the name of that revision
in the following command:
gcloudrunrevisionsdescribeREVISION
Replace REVISION with the name of the revision you want to
learn more about.
gcloudrunrevisionsdescribeREVISION--formatyaml
Note that a non-current revision may have the status of RETIRED, which means
that Knative serving has retired the infrastructure needed for that
particular revision.
About build and source repository information in the Details panel
If the
Artifact Analysis API
is enabled and the container was built with Cloud Build,
build information is displayed in the Details panel.
Additionally, if a
Cloud Build trigger
was used to build the container, source repository information is also displayed
in the Details panel.
Deleting revisions
A common use case for deleting a revision is when you want to make sure a
particular revision won't be accidentally used.
You cannot delete a revision if:
it is able to receive traffic,
it is the only revision of the service,
it is the latest revision of the service.
When you delete a revision, the container image used by this revision is not
deleted automatically from Container Registry or Artifact Registry. To delete a
container image from a registry, see the deletion instructions for
Container Registry or
Artifact Registry.
You cannot undo a revision deletion.
You can use either the console or the command line:
Console
To delete a revision:
Go to Knative serving in the Google Cloud console:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 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)"]]
