Managing Canary Releases with Cloud Run Traffic Splitting
Learn how to use Cloud Run traffic splitting to implement canary releases, reducing deployment risk by routing small percentages of traffic to new revisions before a full rollout.
Loading…
ReadMeFeed / Community knowledge
#traffic-splitting
Real questions. Useful conversations. Find the people who know your stack.
cloudrunUsing Traefik Mesh Weighted Traffic Splitting for Safe Canary Deployments
Learn how to shift a fraction of traffic to a new service version with Traefik Mesh’s TrafficSplit resource, verify the split with Prometheus metrics, and understand the operational constraints.
traefikmeshApplication Gateway Traffic Splitting vs. SSH Tunneling for Non-HTTP Zero-Downtime Migration
Migration Goal and Constraint A small Teleport-managed application must be migrated to new instances with zero downtime. Teleport's Application Gateway (introduced in v12) provides HTTP(S) traffic splitting, allowing gradual shift of web traffic while preserving SSO sessions and identity mappings. Protocol Limitation The Application Gateway only supports HTT
teleport
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 revi
Cloud Run Traffic Splitting: Need for Fractional Percentages in Version 1.x
Goal Enable precise, non‑integer traffic allocation to revisions for canary and blue‑green deployments, such as 33.3%/33.3%/33.4% splits. Constraints The current Cloud Run Traffic Splitting API accepts only whole‑percentage values (e.g., 25%, 75%). Both the gcloud CLI and Cloud Console reject decimal inputs with validation errors. No public roadmap or releas
Moleculer API Gateway Version Routing Lacks Configurable Traffic Split
Moleculer API Gateway Version Routing Lacks Configurable Traffic Split The goal is to enable a gradual, percentage‑based shift of incoming requests from an existing service version to a new version while keeping both versions deployed in the same Moleculer broker, using only the framework’s built‑in API gateway. Currently the gateway can route to a specific
Cloud Run and Cloud Monitoring alert scoping across traffic-split revisions
Goal: configure a Cloud Monitoring alert policy for a Cloud Run service that evaluates request latency or error rate while traffic is split across multiple revisions, without generating a separate alert for every revision or firing during scale-to-zero gaps. Cloud Run emits request count, latency, and container utilization to Cloud Monitoring. Alert conditio