---
title: "Discussion on \"Continuous Deployment to Cloud Run Services based on a New Container Image.\" | Hashnode"
description: "Discussion on \"Continuous Deployment to Cloud Run Services based on a New Container Image.\". This article explains an approach to continuously deploy revisions to Cloud Run service(s) based on a new container image.\n\nContinuous Deployment\nContinuous deployment is a strategy for software releases wherein any code commit that passes the automa..."
url: "https://hashnode.com/posts/continuous-deployment-to-cloud-run-services-based-on-a-new-container-image/5d436ebb0754e2be741cc390"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Continuous Deployment to Cloud Run Services based on a New Container Image.](https://fullstackgcp.timtech4u.dev/continuous-deployment-to-cloud-run-services-based-on-a-new-container-image?utm_source=hashnode&utm_medium=feed)

This article explains an approach to continuously deploy revisions to Cloud Run service(s) based on a new container image. Continuous Deployment Continuous deployment is a strategy for software releases wherein any code commit that passes the automa...

Aug 1, 2019 · fullstackgcp.timtech4u.dev  
Read the article

-   [#google-cloud](https://hashnode.com/tag/google-cloud)
-   [#docker](https://hashnode.com/tag/docker)
-   [#continuous-deployment](https://hashnode.com/tag/continuous-deployment)

## Written by

[Timothy Olaleke](https://hashnode.com/@timtech4u)

@timtech4u · Kano, Nigeria

  
[View profile](https://hashnode.com/@timtech4u)

Software Developer & Google Developer Expert for Cloud

Tim is a software developer who builds awesome stuff, he has a wide experience in building customer-based solutions for digital needs using mind-blowing technologies. He is also a DevOps Enthusiast with a passion for automation and an open-source hobbyist, in his free time, he writes a lot of Google Cloud related tutorials and makes open contributions on GitHub. Tim is an active member of various developers communities, where he focuses on making impacts and sharing his experiences whilst learning.

## Responses 1

Markdown supported · ⌘↵ to post

[Blaine Garrett](https://hashnode.com/@blainegarrrett)

[Dec 18, 2019](https://hashnode.com/posts/continuous-deployment-to-cloud-run-services-based-on-a-new-container-image/5d436ebb0754e2be741cc390/comment/5dfa2d31066598ab2752cc49)

Great article! As a long time App Engine developer, one thing I don't understand about Cloud Run's deployment process is version switching. With App Engine, I could could deploy a release to both QA and Production but not migrate traffic on the later. Once automation tests were run on QA environment and some manual smoke tests, then we would migrate traffic to already deployed version. It was just a few clicks at that point.

So far as I can tell with Cloud Run, there are "revisions" but no concept of traffic splitting, migration, or the default "instance" so that you can quickly switch over to an already deployed (and warmed up) "instance".

Do you have any insight or best practice advice on this?

[Timothy Olaleke](https://hashnode.com/@timtech4u)

[Dec 21, 2019](https://hashnode.com/posts/continuous-deployment-to-cloud-run-services-based-on-a-new-container-image/5d436ebb0754e2be741cc390/comment/5dfa2d31066598ab2752cc49#reply-5dfdc52e339f878d7266dccd)

Hi Blaine,

Thanks for reading up and making such an awesome comment.

Cloud Run currently only supports serving traffic from the last healthy revision of your service. Therefore, it currently does not support revision based traffic splitting and canary deployments.

You can take a look at this issue: [issuetracker.google.com/issues/144717649](https://issuetracker.google.com/issues/144717649)

Cheers
