Using Traefik Mesh TrafficSplit for Safe Canary Deployments
Learn how Traefik Mesh TrafficSplit enables weighted canary releases without code changes, including setup, verification via Prometheus, and key limitations.
Loading…
ReadMeFeed / Community knowledge
#trafficsplit
Real questions. Useful conversations. Find the people who know your stack.
traefikmeshTraefik Mesh TrafficSplit weight normalization produces different routing in test vs production
Goal: achieve identical traffic percentages for each backend defined in a TrafficSplit resource when the same weight values are applied across different cluster environments. Constraint: Traefik Mesh v1.2.x normalizes weights using integer division, while v1.4.x uses floating‑point arithmetic followed by nearest‑integer rounding, which can shift the effectiv
Does Traefik Mesh support automatic rollback of TrafficSplit on health‑check failure?
Traefik Mesh’s TrafficSplit resource enables weighted traffic shifting between service versions, but the current implementation does not automatically modify weights in response to health‑check failures or other observability signals. Operators must manually adjust the TrafficSplit or delete it to revert traffic, which can delay reaction to a failing version
TrafficSplit zero-healthy-endpoint ambiguity in Traefik Mesh controller
Traefik Mesh implements the SMI TrafficSplit spec by translating TrafficSplit custom resources into Traefik dynamic configuration, programming the data plane with a weighted load balancer across split backends. When one backend in a TrafficSplit has zero healthy endpoints, the redistribution behavior is not clearly documented: it is ambiguous whether the sur