linkerd / linkerd/linkerd2

Tab / Mirror of traffic

Open
#4,385 7 comments 17 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/controller area/proxy help wanted
Dominant language
Go
Stars
11.5k
Forks
1.4k
Avg merge
3d 22h
Merged PRs (30d)
53

Description

## Feature Request
We would like to have the ability to mirror traffic to one service to another url

### What problem are you trying to solve?
This would solve an issue where we want to either test a new version with production traffic or alternatively debug an issue by using production traffic

### How should the problem be solved?
Either by extending the traffic split to allow mirroring

What do you want to happen? Add any considered drawbacks.
The traffic from one service gets mirrored to another service

### Any alternatives you've considered?
We have tried to use tap but for debugging, which would solve one half of the problem.
The issue is that tap doesn't allow to see the POST request body so we can't see whats being sent in and what is responded

Is there another way to solve this problem that isn't as good a solution?

### How would users interact with this feature?

If you can, explain how users will be able to use this. Maybe some sample CLI
output?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing traffic-split behavior and the tap approach described in the issue. Determine how mirrored requests, including POST bodies and responses, should reach another service URL without affecting the primary request. Done means the interaction and trade-offs are specified and traffic can be mirrored reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.