IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:

To solve the issue of version skew, when a new revision is released but clients loaded an old revision, it would be helpful to route requests based on headers or automatically include cookies to ensure clients can still access old revisions automatically, and only receive new revisions once they have created a new session.

This is similar to Vercels Skew Protection. Session Affinity seems to be at the instance level, whereas this feature would be at the revision level.

How this might work:

Access an environment variable in a Cloud Run instance such as CLOUD_RUN_REVISION_ID, if a client then attaches it to a header such as x-cloud-run-revision it would then route traffic to the revision. If the revision does not exist it routes to the latest revision.

If applicable, reasons why alternative solutions are not sufficient:

Session Affinity operates at the instance level, however, if this is to run at the revision level, regardless of the instance.

Other information (workarounds you have tried, documentation consulted, etc): I have researched but found no solution