Cloud Run traffic routing and prior revision rollback behavior
The goal is to determine the reliability of reversing a failed Cloud Run deployment by manually shifting 100% of traffic back to a previous immutable revision. In fully managed Cloud Run, the service does not natively migrate traffic away from a new revision if the container instances crash or return consistent 5xx errors. Traffic remains assigned to the lat
cloudrun