Skip to content

Containers · 4 November 2026

Cloud Run revisions are named, and traffic can be pinned to one

In the Google Cloud Run Admin API at /compat/google-cloud-run, each version of a Container is a revision named <service>-<version>, such as hello-3. In v2, a service now returns latestCreatedRevision (the newest version), latestReadyRevision (the version serving requests) and trafficStatuses. In v1, it returns status.latestCreatedRevisionName, status.latestReadyRevisionName and status.traffic[].revisionName. Sending 100% of traffic to one revision sets the Container's spec.version, which rolls it back to that version: in v2, traffic with type: TRAFFIC_TARGET_ALLOCATION_TYPE_REVISION and revision; in v1, spec.traffic with revisionName, as gcloud run services update-traffic --to-revisions hello-2=100 sends. Traffic to the latest revision (TRAFFIC_TARGET_ALLOCATION_TYPE_LATEST, or latestRevision: true) removes the pin. A revision of another service, a revision without a version number, or a revision named in a create returns 400. A traffic split between revisions returns 400, and revisions.list, revisions.get and revisions.delete are not yet available.

Same day.

Cut your cloud billby 75%.

No card to start. Billed by the second after.

Start free, no card