linkerd/linkerd

This system is a service mesh infrastructure that provides dynamic service discovery, routing, and protocol translation for distributed applications. It manages name resolution across diverse backends like Kubernetes, Consul, and ZooKeeper, while offering a centralized delegation service (Namerd) to configure routing rules. The platform supports multiple protocols including HTTP/2, gRPC, and Thrift, with built-in observability for metrics, tracing, and logging.

This period focused on introducing Namerd as a dedicated service for managing name delegation and configuration, alongside a major expansion of supported protocols including Thrift, HTTP/2, and Consul. The team also overhauled the admin interface, refactored the internal configuration and initialization architecture, and added extensive test coverage for these new features.

100 changes

This period focused on implementing full HTTP/2 and gRPC protocol support within Finagle and Linkerd, including Netty4-based transports, response classification, and failure accrual. The work also expanded the admin dashboard with service-oriented views and introduced new telemetry providers for StatsD, InfluxDB, and Prometheus.

60 changes

This period focused on expanding service discovery capabilities by adding support for Rancher, Marathon, and Consul backends, alongside a new gRPC-based destination interface. The admin interface was enhanced to expose internal namer state and delegate configurations, while error messaging and test coverage were improved for better diagnostics and security.

8 changes

linkerd/linkerd was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.