Health check failure: Cloud Run revision upgrade recovery

Goal

Safely recover from a Cloud Run revision that fails health checks after an upgrade, ensuring minimal service disruption and preserving request integrity.

Constraints & Uncertainty

Cloud Run’s traffic‑splitting feature allows a new revision to receive a percentage of traffic, but the platform does not automatically revert traffic to the previous revision when health checks fail. Operators must manually adjust traffic weights via the console or gcloud, and there is no built‑in alert that forces a rollback. This lack of automatic rollback can expose services to prolonged failure periods if operators overlook manual intervention.

Unresolved Questions

• Should we implement an automated traffic shift when a revision consistently fails health checks?
• What monitoring thresholds or alerting patterns best indicate a need for manual rollback?
• Does Cloud Deploy’s canary release workflow provide a more reliable rollback mechanism compared to native Cloud Run traffic splitting?