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
update 1.x README to point to 2.x repo #2416
Conversation
Signed-off-by: William Morgan <william@buoyant.io>
Just 5c: I don't concur with the new wording: linkerd2 is not a replacement for linkerd1. |
Thanks for the feedback @peterfroehlich. I also love Linkerd 1.x and am glad to hear it continues to work for you. I'm open to suggestions for better wording. The original maintainers of 1.x are now all working on 2.x, or on other things, and the change is meant to reflect that. Leaving the page as is also doesn't feel right, as there are currently no active maintainers. (Also, I would love to add some 1.x maintainers if you are interested in having that discussion.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about this?
HTTP/gRPC/thrift/etc proxy, and can usually be dropped into existing | ||
applications with a minimum of configuration, regardless of what language | ||
they're written in. It works with many common protocols and service discovery | ||
backends, including scheduled environments like Mesos and Kubernetes. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its fully featured with powerful load balancing algorithms, failure handling, instrumentation, | |
distributed tracing and dynamic request routing. | |
It also offers a stand-alone version of the service discovery components called Namerd, | |
which enables a scalable architecture with centralised namers and a simple api for adaptation | |
to other load balancing systems. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a nice description, just a bit of punctuation that is missing:
Linkerd is fully featured with powerful load balancing algorithms, failure handling, instrumentation,
distributed tracing, and dynamic request routing.
It also offers a stand-alone version of the service discovery components, called Namerd,
which enables a scalable architecture with centralised "namers" and a simple api for adaptation
to other load balancing systems.
I've submitted a review, tried to move k8 user to linkerd2 without scaring away other parties.
I don't have experience in that role, but my team at work has multiple Maintainers of OSS projects. I'll discuss with them and come back to you. |
Co-authored-by: Peter Fröhlich <tarwin@tarwin.de>
Did a little more wordsmithing to clarify what this repo is currently used for. |
Thanks for including my text! ❤️ |
Signed-off-by: William Morgan william@buoyant.io