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
Cheers
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?