Off-cluster support for linkerd2-proxy
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
What problem are you trying to solve?
I want to be able to run linkerd2-proxy as a standalone binary, without a Kubernetes cluster.
See the "Off-cluster support" section in https://linkerd.io/2020/09/02/the-road-ahead-for-linkerd2-proxy/ article.
See also these (more or less related) issues
My personal motivation for wanting this is that I am writing TCP proxies and I want to have a simple way to benchmark against linkerd2-proxy.
How should the problem be solved?
The two linked issues I mentioned should pretty much take care of this, I hope.
Any alternatives you've considered?
I did not consider alternatives.
How would users interact with this feature?
No response
Would you like to work on this feature?
maybe
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
Start by reading the linked “Off-cluster support” article and issues 2449 and 2048 to understand the proposed scope. The work is complete when linkerd2-proxy can run as a standalone binary without a Kubernetes cluster and the relevant behavior is covered by tests, though no files or tests are named here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100