-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Developer Documentation #2449
Comments
I definitely agree that the internal architecture of the proxy codebase ought to be better documented! Regarding docs for how to run the proxy, are there |
@hawkw Makefile targets would be great as that is where one will likely be looking first when looking to contribute. There likely needs to be some accompanying documentation. For example if I start up the proxy with
Then I refer back to the code I notice that I also refer back to the code and notice V4(0.0.0.0:4143) is the inbound_listener pipeline and assume it is for reverse proxying inbound requests. So, I also have debug symbols on so I can step through the code and observe.
Now, I spin up some http service with docker: I also want to inspect the proxy behavior for the reverse proxy functionality. This kind of process should be documented somewhere IMO. |
I absolutelly support that. As a new commer lurking around the code its quite hard for me to grasp the basic data pipeline. As a matter of fact a write up that is something like "The life of a request" will be very useful. Just tracking what happens when an http request hits a pod, how is that instrumented relayed, etc as well as providing pointers to concrete parts of the code will be super useful. That will certainly make it a lot easier for people to get started working with the codebase. |
Feature Request
The Linkerd2-Proxy needs better developer documentation. Empower contributors to be able to work in the productivity fast lane
What problem are you trying to solve?
Contributing developers should be able to read docs that demonstrate a simple setup in order to easily build, run and debug the proxy inside and outside of a k8s environment.
How should the problem be solved?
The Linkerd2-Proxy repo needs good developer documentation allowing them to:
There should be some canned dev environment / setups documented that allow developers to get up and running in development mode with minimal dependencies.
Any alternatives you've considered?
How would users interact with this feature?
By reading and following documentation. :)
The text was updated successfully, but these errors were encountered: