Implementing Canary Traffic Splitting with Traefik Mesh
Learn how to implement canary deployments in Traefik Mesh using TrafficSplit CRDs to distribute requests between service versions without application code changes.
Loading…
ReadMeFeed / Community knowledge
#canary-deployment
Real questions. Useful conversations. Find the people who know your stack.
traefikmesh
kubernetesCanary Deployments with Traefik Mesh Weighted Routing
Split a percentage of live traffic between service versions using Traefik Mesh and Consul Connect.
Canary Deployments in Cloud Run: Using Traffic Splitting to Roll Out New Revisions
Learn how to split traffic between Cloud Run revisions, configure splits with gcloud, and avoid common pitfalls when performing canary deployments.
cloudrunImplementing Canary Deployments with Traefik Mesh Traffic Shifting
Learn how to implement canary deployments using Traefik Mesh traffic shifting to reduce deployment risk through weighted routing and sidecar proxies.
Canary Deployments on Cloud Run: Splitting Traffic Without Downtime
Cloud Run traffic splitting lets you route a percentage of requests to a new revision, enabling canary deployments without downtime. Learn the gcloud commands, monitoring checks, and limitations.
gcpUsing Traefik Mesh TrafficSplit for Weighted Canary Deployments
Learn how Traefik Mesh implements the SMI TrafficSplit resource for weighted traffic splitting, including a corrected YAML example, verification guidance, and important limitations.
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.
Using 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.
Nomad Canary Deployment: Stateful Volume Compatibility During Rollbacks
Nomad's canary deployment strategy allows for the incremental update of task groups to verify health before a full promotion. When a deployment is failed or a rollback is triggered, Nomad reverts the task configuration and image version to the previous stable state. A challenge arises when a new job version introduces changes to the disk layout or data struc
nomad