Linkerd is a transparent service mesh, designed to make modern applications safe and sane by transparently adding service discovery, load balancing, failure handling, instrumentation, and routing to all inter-service communication.
Linkerd (pronouned "linker-DEE") acts as a transparent 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.
Linkerd is hosted by the Cloud Native Computing Foundation (CNCF).
Want to try it?
For instructions on how to configure and run Linkerd, see the user documentation on linkerd.io.
Working in this repo
BUILD.md includes general information on how to work in this repo. Additionally, there are documents on how to build several of the application subprojects:
- linkerd -- produces
- namerd -- produces
namerdservice discovery artifacts
- grpc -- produces the
- linkerd-examples: A variety of configuration examples and explanations
- linkerd-tcp: A lightweight TCP/TLS load balancer that uses Namerd
- linkerd-viz: Zero-configuration service dashboard for Linkerd
- linkerd-zipkin: Zipkin tracing plugins
- namerctl: A commandline utility for controlling Namerd
Code of Conduct
This project is for everyone. We ask that our users and contributors take a few minutes to review our code of conduct.
Copyright 2018, Linkerd Authors. All rights reserved.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use these files except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.