trafficsplit based on sourcelabels? like istio
Open
Nobody has claimed this yet.
needs/design
pinned
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
Discussed in https://github.com/linkerd/linkerd2/discussions/7081
Originally posted by hawk-liu October 12, 2021
we are trying linkerd for our app.
but we want serviceA-canary->serviceB-canary->serviceC-canary, not serviceA-canary->serviceB-pro->serviceC-pro.
the doc only show trafficsplit based http header/weight, is there any way like istio sourcelabel solution?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no file or test entry point. Start by reading the existing TrafficSplit documentation and the linked discussion, then determine the agreed scope for source-label-based routing across canary services. Done means the requested behavior is either supported with coverage or its limitations are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100