Ask questionsHeader based routing
We would like to route requests to a service via headers on inbound requests!
There exists an open issue on the SMI spec that details how A/B testing could be extended to support cookies/headers/etc, instead of just weights: https://github.com/deislabs/smi-spec/issues/17.
As the SMI spec evolves beyond weighted traffic routing ie A/B or canary deployments like the linked issue above describes, it would be useful to be able to route traffic to backing services based on headers. At present, Linkerd does not support this feature, but Istio's virtualservice does - but we'd much rather use linkerd than take on istio.
Our use case, I think, is straightforward:
This issue was opened, and it seems like the Traffic Split SMI resource mostly resolved issues in this situation, but in it's current form will not be sufficient to address the implementation we desire.
If the API described in this issue is comprehensive enough, it would be sufficient.
Here is an example of usage that I'd like to see; an example of traffic split between 3 backing services:
apiVersion: v1beta1 kind: TrafficSplit metadata: name: frontend spec: service: frontend backends: - service: primary-frontend - service: beta-frontend matchRegex: - name: "beta users" x-group: "beta-users" # users who signed up for the beta - service: alpha-frontend matchRegex: - name: "alpha users" x-group: "alpha-users" # users who want to live on the bleeding edge
Answer questions stale[bot]
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.