Console

1. In the Google Cloud console, go to the Cloud RunServices page:

   Go to Cloud Run

2. Locate the service in the services list, and click it.

3. Click theRevisions tab to show the list of current revisions for thatservice.

4. In the list of revisions, click the ellipsis icon to the right of therevision you are rolling back:

   

5. ClickManage Traffic to display the manage traffic form:

   1. Select the previous revision you want to roll back to in the drop-downlist.
   2. Set that previous revision's traffic percentage to 100.
   3. Set the currently serving revision's percentage to 0.
   4. ClickSave.

gcloud

Use the following command:

gcloudrunservicesupdate-trafficSERVICE--to-revisionsREVISION=100

• ReplaceSERVICE with the name of the service.
• ReplaceREVISION with the name of the revision you are rolling back to.

YAML

1. If you are creating a new service, skip this step.If you are updating an existing service, download itsYAML configuration:

   gcloudrunservicesdescribeSERVICE--formatexport>service.yaml

2. Below thespec attribute, locate and update thetraffic attribute tothe following:

   apiVersion:serving.knative.dev/v1kind:Servicemetadata:name:SERVICEspec:...traffic:-revisionName:REVISIONpercent:100

   Replace

   • REVISION with the name of the revision you are rolling back to.

3. Replace the service with its new configuration using the following command:

   gcloudrunservicesreplaceservice.yaml

4. Wait for the update to complete: you should see a message that therevision you are rolling backfrom has been deployed and is serving0 percent of traffic.

Terraform

To learn how to apply or remove a Terraform configuration, seeBasic Terraform commands.

resource"google_cloud_run_v2_service""default"{name="my-service"location="us-central1"deletion_protection=false # set to true to prevent destruction of the resourcetemplate{}traffic{percent=100    # This revision needs to already existrevision="green"type="TRAFFIC_TARGET_ALLOCATION_TYPE_REVISION"}}

Console

1. In the Google Cloud console, go to the Cloud RunServices page:

   Go to Cloud Run

2. Select a service in the services list.

3. ClickDeploy New Revision.

4. Fill out the deploy form as needed, but make sure the checkbox labelledServe this revision immediately is UNCHECKED.

5. ClickDeploy.

6. ClickManage Traffic.

7. The new revision is listed but with a 0 percentage set: it is currentlynot serving any traffic. In the form:

   1. Set it to the desired percentage, forexample, 5. Note that the currently serving version's percentage isautomatically reduced by that same amount.
   2. ClickSave.
   3. Repeat theseManage Traffic steps but with changed percentages,increasing the percentage as needed for the new revision. You do notneed to redeploy to change the traffic percentages.

gcloud

To deploy a service from a container image:

1. Deploy the revision you want to roll out gradually, initially settingit to receive no traffic:

   • To deploy a service from source code:

     gcloudrundeploy--imageIMAGE--no-traffic

     ReplaceIMAGE with the image you are deploying.

   • To deploy a service from source code:

     gcloudrundeploySERVICE--source.--no-traffic

     ReplaceSERVICE with the name of your service.

2. Specify the percentage of traffic you want the new revision to handle,for example, 5 percent:

   gcloudrunservicesupdate-trafficSERVICE--to-revisionsREVISION=PERCENTAGE

   • ReplaceSERVICE with the name of the service.
   • ReplaceREVISION with the name of the revision you arerolling out gradually. To specify the latest revision, you can useLATEST, for example,LATEST=5.
   • ReplacePERCENTAGE with the percentage of traffic you wantto send to the new revision, for example,5 to send it 5% of traffic.

3. After the revision's performance is satisfactory, repeat the precedingupdate-traffic step, but increase the percentage value as desired.

YAML

1. If you are creating a new service, skip this step.If you are updating an existing service, download itsYAML configuration:

   gcloudrunservicesdescribeSERVICE--formatexport>service.yaml

2. Make any desired configuration changes to the service, and specify therevision name you want for the new revision:

   apiVersion:serving.knative.dev/v1kind:Servicemetadata:name:SERVICEspec:template:metadata:annotations:...name:REVISION-NAME

   Replace

   • REVISION-NAME with the name you want the new revision tohave.

3. Below thespec attribute, locateand update thetraffic attribute so that the new revision serves only asmall amount of traffic:

   apiVersion:serving.knative.dev/v1kind:Servicemetadata:name:SERVICEspec:...traffic:-revisionName:REVISION-NEWpercent:PERCENT-NEW-revisionName:REVISION-FORMERpercent:PERCENT-FORMER

   Note that the percentages must add up to 100. Replace

   • REVISION-NEW with the name of the revision you are rolling outgradually.
   • REVISION-FORMER with the name of the currently serving revision.
   • PERCENT-NEW with the traffic percentage you want to send to the new revision,for example use10 to send 10% of the traffic to that revision.
   • PERCENT-FORMER with the traffic percentage you want to send to the old revision

4. Wait for the update to complete: you should see a message that thenew revision you are gradually rolling out has been deployed and is servingthe traffic percentage value you used.

Terraform

Add the following to your.tf file and gradually update the traffic percentage from previous revision to thelatest revision.Keep in mind that every traffic change will require anotherterraform apply to be executed.

resource"google_cloud_run_v2_service""default"{name="my-service"location="us-central1"deletion_protection=false # set to true to prevent destruction of the resourcetemplate{containers{      # Image or image tag must be different from previous revisionimage="us-docker.pkg.dev/cloudrun/container/hello"}}  # Define the traffic split for each revision  # https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service#traffictraffic{percent=100    # This revision needs to already existrevision="green"type="TRAFFIC_TARGET_ALLOCATION_TYPE_REVISION"}traffic{    # Deploy new revision with 0% trafficpercent=0type="TRAFFIC_TARGET_ALLOCATION_TYPE_LATEST"}}

Apply the changes by enteringterraform apply.

Console

1. In the Google Cloud console, go to the Cloud RunServices page:

   Go to Cloud Run

2. Locate the service in the services list, and click on it.

3. ClickManage Traffic.

4. The currently serving new revision is listed. In the form:

   1. Set the currently serving revision percentage to the desired split.
   2. Select one of the previous revisions using the dropdown list and setit to the desired percentage split.
   3. To split traffic between more revisions, clickAdd Revision,select the desired revision, and set the percentage to the desired split.
   4. ClickSave.

gcloud

Specify the revisions and the percentage of traffic for each revision in acomma delimited list:

gcloudrunservicesupdate-trafficSERVICE--to-revisionsLIST

• ReplaceSERVICE with the name of the service.
• ReplaceLIST with a comma delimited list of revisions andpercentages:
  REVISION1=PERCENTAGE1,REVISION2=PERCENTAGE2,REVISIONn=PERCENTAGEx
  for example,hello2-00005-red=25,hello2-00001-bod=25,hello2-00002-nan=50.

YAML

1. If you are creating a new service, skip this step.If you are updating an existing service, download itsYAML configuration:

   gcloudrunservicesdescribeSERVICE--formatexport>service.yaml

2. Below thespec attribute, locateand update thetraffic attribute so that the new revision serves only asmall amount of traffic:

   apiVersion:serving.knative.dev/v1kind:Servicemetadata:name:SERVICEspec:...traffic:-revisionName:REVISION-Apercent:PERCENT-A-revisionName:REVISION-Bpercent:PERCENT-B-revisionName:REVISION-Cpercent:PERCENT-C

   Note that percentages must add up to 100. Replace

   • REVISION-A,REVISION-B,REVISION-Cwith the revisions you are allotting traffic to.
   • PERCENT-A,PERCENT-B,PERCENT-C withthe percentage for the corresponding revision.

3. Replace the service with its new configuration using the following command:

   gcloudrunservicesreplaceservice.yaml

4. Wait for the update to complete: you should see a message that thenew revision you are gradually rolling out has been deployed and is serving5 percent (or whatever gradual value you used) of traffic.

Terraform

Add the following to your.tf file:

resource"google_cloud_run_v2_service""default"{name="my-service"location="us-central1"deletion_protection=false # set to true to prevent destruction of the resourcetemplate{containers{image="us-docker.pkg.dev/cloudrun/container/hello"}revision="green"}  # Define the traffic split for each revision  # https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service#traffictraffic{percent=25revision="green"type="TRAFFIC_TARGET_ALLOCATION_TYPE_REVISION"}traffic{percent=75    # This revision needs to already existrevision="blue"type="TRAFFIC_TARGET_ALLOCATION_TYPE_REVISION"}}

Apply the changes by enteringterraform apply.

Console

1. In the Google Cloud console, go to the Cloud RunServices page:

   Go to Cloud Run

2. Locate the service in the services list, and click it.

3. ClickDeploy New Revision.

4. Fill out the deploy form as needed, making sure you check thecheckbox labelledServe this revision immediately. This will override anyexisting traffic splitting, with the new revision serving 100 percent oftraffic.

5. ClickDeploy.

gcloud

To send all traffic to the most recently deployed revision:

gcloudrunservicesupdate-trafficSERVICE--to-latest

ReplaceSERVICE with the name of the service.

YAML

1. If you are creating a new service, skip this step.If you are updating an existing service, download itsYAML configuration:

   gcloudrunservicesdescribeSERVICE--formatexport>service.yaml

2. Below thespec attribute, locateand update thetraffic attribute to the following

   apiVersion:serving.knative.dev/v1kind:Servicemetadata:name:SERVICEspec:...traffic:-latestRevision:truepercent:100

3. Replace the service with its new configuration using the following command:

   gcloudrunservicesreplaceservice.yaml

4. Wait for the update to complete: you should see a message that the(latest) revision is deployed and is serving100 percent of traffic.

Terraform

Add the following to your.tf file:

resource"google_cloud_run_v2_service""default"{name="my-service"location="us-central1"deletion_protection=false # set to true to prevent destruction of the resourcetemplate{}traffic{percent=100type="TRAFFIC_TARGET_ALLOCATION_TYPE_LATEST"}}

Apply the changes by enteringterraform apply.

gcloud

gcloudrundeploymyservice--imageIMAGE_URL--no-traffic--tagTAG_NAME

Replace:

• IMAGE_URL with the URL for your image.
• TAG_NAME with your lowercase tag name.

The tag lets you directly test the new revision at a specific URL, withoutserving traffic. The URL starts with the tag name you provided: for exampleif you used the tag namegreen on the servicemyservice, you wouldtest the tagged revision at the URLhttps://green---myservice-abcdef.a.run.app

YAML

1. If you are creating a new service, skip this step.If you are updating an existing service, download itsYAML configuration:

   gcloudrunservicesdescribeSERVICE--formatexport>service.yaml

2. Below thetraffic attribute, locate and update thetag attributethat corresponds to the revision that you want to add a tag to:

   apiVersion:serving.knative.dev/v1kind:Servicemetadata:name:SERVICEspec:...traffic:-revisionName:REVISIONpercent:100-revisionName:REVISION-Atag:TAG-A-revisionName:REVISION-Btag:TAG-B-revisionName:REVISION-Ctag:TAG-C

   Replace:

   • TAG-A,TAG-B,TAG-C with the tagassociated to each revision.
   • REVISION with the name of an existing revision that youwant to send all of the traffic to.

3. Create or update the service using the following command:

   gcloudrunservicesreplaceservice.yaml

Terraform

Add the following to your.tf file and gradually update the traffic percentage from old revision to the newest revision with the newtag.Keep in mind that every traffic change will require anotherterraform apply to be executed.

resource"google_cloud_run_v2_service""default"{name="my-service"location="us-central1"deletion_protection=false # set to "true" in productiontemplate{containers{      # image or tag must be different from previous revisionimage="us-docker.pkg.dev/cloudrun/container/hello"}revision="blue"}  # Define the traffic split for each revision  # https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service#traffictraffic{percent=100    # This revision needs to already existrevision="green"type="TRAFFIC_TARGET_ALLOCATION_TYPE_REVISION"}traffic{    # Deploy new revision with 0% trafficpercent=0revision="blue"tag="tag-name"type="TRAFFIC_TARGET_ALLOCATION_TYPE_REVISION"}}

Apply the changes by enteringterraform apply.

Console

1. In the Google Cloud console, go to the Cloud RunServices page:

   Go to Cloud Run

2. Select a service in the services list.

3. Navigate to theRevisions section within your desired service and select the revision for which you would like to remove the existing tag.

4. Hold the pointer over theRevision URLs (tags) column and click the pencil icon:

   

5. In theRevision URLs dialog menu, click theBin icon to remove the current tag used in your revision.

6. ClickSave.

gcloud

To remove a revision tag:

gcloudrunservicesupdate-trafficSERVICE--remove-tagsTAG_NAME

Replace

• TAG_NAME with the name of the tag you are migrating traffic to
• SERVICE with the name of the service you are removing the tag from

YAML

1. If you are creating a new service, skip this step.If you are updating an existing service, download itsYAML configuration:

   gcloudrunservicesdescribeSERVICE--formatexport>service.yaml

2. Make any desired configuration changes to the service.

3. Below thespec attribute, locateand remove thetag attribute for the tagged revision:

   apiVersion:serving.knative.dev/v1kind:Servicemetadata:name:SERVICEspec:...traffic:-revisionName:REVISIONtag:TAG_NAMEpercent:PERCENT-NEW

4. Replace the service with its new configuration using the following command:

   gcloudrunservicesreplaceservice.yaml

Terraform

Add the following to your.tf file:

resource"google_cloud_run_v2_service""default"{name="my-service"location="us-central1"deletion_protection=false # set to true to prevent destruction of the resourcetemplate{}  # Define the traffic split for each revision  # https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service#traffictraffic{percent=100    # This revision needs to already existrevision="green"type="TRAFFIC_TARGET_ALLOCATION_TYPE_REVISION"}traffic{    # No tags for this revision    # Keep revision at 0% trafficpercent=0    # This revision needs to already existrevision="blue"type="TRAFFIC_TARGET_ALLOCATION_TYPE_REVISION"}}

Apply the changes by enteringterraform apply.

Console

1. In the Google Cloud console, go to the Cloud RunServices page:

   Go to Cloud Run

2. Locate the service in the services list, and click it:

3. Select the tagged revision you want to send traffic to:

   

4. ClickManage Traffic.

5. Locate the tagged revision name: it is listed but with a 0 percentage set:it is currently not serving any traffic. In theManage traffic* form:

   1. Set it to the desired percentage, forexample, 5. Note that the currently serving version's percentage isautomatically reduced by that same amount.
   2. ClickSave.
   3. Over a period of hours or days, as needed, repeat theseManage Traffic steps but with changed percentages,increasing the percentage as needed for the tagged revision. You do notneed to redeploy to change the traffic percentages.

gcloud

To migrate traffic to a specific revision tag:

gcloudrunservicesupdate-trafficmyservice--to-tagsTAG_NAME=TRAFFIC_PERCENT

Replace

• TAG_NAME with the name of the tag you are migrating traffic to
• TRAFFIC_PERCENT with the percentage of traffic you want tothe tagged revision to serve, for example,1.

YAML

1. If you are creating a new service, skip this step.If you are updating an existing service, download itsYAML configuration:

   gcloudrunservicesdescribeSERVICE--formatexport>service.yaml

2. Make any chosen configuration changes to the service.

3. Below thespec attribute, locateand update thetraffic attribute for the tagged revision so that the taggedrevision serves only a small amount of traffic:

   apiVersion:serving.knative.dev/v1kind:Servicemetadata:name:SERVICEspec:...traffic:-revisionName:REVISIONtag:TAG_NAMEpercent:PERCENT-NEW-revisionName:REVISION-FORMERpercent:PERCENT-FORMER

   Note that the percentages must add up to 100. Replace

   • REVISION with the name of the tagged revision.
   • TAG_NAME with the name of the tag you are rolling outgradually.
   • PERCENT-NEW with the traffic percentage you want to send tothe tagged revision, for example use10 to send 10% of the traffic to that revision.
   • REVISION-FORMER with the name of the currently serving revision.
   • PERCENT-FORMER with the traffic percentage you want to send to the old revision

4. Replace the service with its new configuration using the following command:

   gcloudrunservicesreplaceservice.yaml

5. Wait for the update to complete: you should see a message that thenew revision you are gradually rolling out has been deployed and is servingthe traffic percentage value you used.

Terraform

Add the following to your.tf file:

resource"google_cloud_run_v2_service""default"{name="my-service"location="us-central1"deletion_protection=false # set to true to prevent destruction of the resourcetemplate{}  # Define the traffic split for each revision  # https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_run_v2_service#traffictraffic{    # Update revision to 50% trafficpercent=50    # This revision needs to already existrevision="green"type="TRAFFIC_TARGET_ALLOCATION_TYPE_REVISION"}traffic{    # Update tag to 50% trafficpercent=50    # This tag needs to already existtag="tag-name"}}

Over a period of hours or days, as needed, gradually update from one tag to the other, increasing the percentage as needed for the tagged revision.

Apply by enteringterraform apply after every change.