linkerd/linkerd2

Ultralight, security-first service mesh for Kubernetes. Main repo for Linkerd 2.x.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 46 minutes ago
Added to GitGenius on October 15th, 2022
Created on December 4th, 2017
Open Issues & Pull Requests: 207 (+0)
Number of forks: 1,377
Total Stargazers: 11,480 (+0)
Total Subscribers: 193 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.8 days
Mean response time: 161.7 days
90th percentile: 601.4 days
Tracked items: 295

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 82% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "support" is answered fastest, typically in about 27 hours, while "pinned" waits about 6 months. Only 5% of issues opened in the past year have been closed. Three people close 54% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 83
New in 7 days: 1
Closed in 7 days: 5
Avg open age: 1,421 days
Stale 30+ days: 73
Stale 90+ days: 57

Recent activity

Opened in 7 days: 1
Closed in 7 days: 5
Comments in 7 days: 4
Events in 7 days: 10

Top labels

  • bug (243)
  • wontfix (180)
  • enhancement (93)
  • help wanted (86)
  • area/proxy (73)
  • area/cli (57)
  • good first issue (54)
  • priority/P0 (52)

Detailed Description

Linkerd is an ultralight, security-first service mesh for Kubernetes that adds critical security, observability, and reliability features to your Kubernetes stack with no code change required.

Linkerd solves the problem of securing and observing microservices communication in Kubernetes clusters without requiring application code modifications. It works by injecting a lightweight data plane proxy into your pods, which transparently handles service-to-service traffic. The control plane manages configuration and policy enforcement across the mesh, enabling features like automatic mutual TLS, traffic splitting, and distributed tracing out of the box.

Linkerd suits teams running Kubernetes who want to add security and observability without rewriting applications. It is particularly valuable for organizations prioritizing minimal resource overhead and straightforward deployment. The tool is designed to be simpler and lighter than some alternatives in the service mesh space, making it accessible to teams without extensive infrastructure expertise.

The project maintains a substantial base of real-world adopters, with almost all open issues raised by outside users rather than the core team. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker is dominated by bug fixes, enhancements, and pinned items, reflecting a focus on stability and addressing user-reported problems.