smi-spec
smi-spec copied to clipboard
Trafficsplit based on sourcelabel?
we are testing linkerd+trafficsplit on our app, which based on springcloud. but we want serviceA-canary->serviceB-canary->serviceC-canary, NOT serviceA-canary->serviceB-pro->serviceC-canary. The doc only show trafficsplit based on http header or weight, is there any way to split traffic by sourcelabel like isito?
@keithmattix points out this is referencing https://istio.io/latest/docs/reference/config/networking/virtual-service/#HTTPMatchRequest
Similar topic: https://github.com/servicemeshinterface/smi-spec/issues/242
Great idea @hawk-liu we are going to discuss some updates to the HTTPRouteGroup in an upcoming session as we are covering other changes to these specs.