I can't seem to figure out how to get two versions of the same Rancher service (traefik backends) listening on the same frontend url but with different weights. Every time I start up the second service all traffic for the frontend goes to it no matter the weight.
Not sure if Traefik will get canary deployments with Rancher natively and can't move to Kubernetes yet so I'm trying to figure out a way to make something work and wanted to get your thoughts.
ServiceA is behind TraefikA using labels, constraints, & metadata.
ServiceB is behind TraefikB using labels, constraints, & metadata.
Using the same URL I want to send 90% of traffic to TraefikA/ServiceA and 10% of traffic to TraefikB/ServiceB.
If I put TraefikC in front of TraefikA & TraefikB is there any way you can think of that I could accomplish this using labels & metadata or would I need to create something in custom config file and rebuild the image?
I can't seem to figure out how to get two versions of the same Rancher service (traefik backends) listening on the same frontend url but with different weights. Every time I start up the second service all traffic for the frontend goes to it no matter the weight.
Not sure if Traefik will get canary deployments with Rancher natively and can't move to Kubernetes yet so I'm trying to figure out a way to make something work and wanted to get your thoughts.
ServiceA is behind TraefikA using labels, constraints, & metadata.
ServiceB is behind TraefikB using labels, constraints, & metadata.
Using the same URL I want to send 90% of traffic to TraefikA/ServiceA and 10% of traffic to TraefikB/ServiceB.
If I put TraefikC in front of TraefikA & TraefikB is there any way you can think of that I could accomplish this using labels & metadata or would I need to create something in custom config file and rebuild the image?