explaingit

linkerd/linkerd2

11,392GoAudience · ops devopsComplexity · 4/5LicenseSetup · hard

TLDR

Linkerd is a lightweight service mesh for Kubernetes that automatically adds encryption, monitoring, and reliability between your app's services without any changes to your application code.

Mindmap

mindmap
  root((Linkerd))
    What it does
      Encrypts traffic
      Service monitoring
      Retry handling
    How it works
      Sidecar proxy in Rust
      Mutual TLS
      Kubernetes install
    Key features
      Zero code changes
      Built-in metrics
      Public security audits
    Tech
      Go control plane
      Rust data proxy
      CNCF project
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Automatically encrypt all traffic between services in a Kubernetes cluster using mutual TLS with zero code changes.

USE CASE 2

Add detailed metrics and dashboards showing which services talk to each other, how long requests take, and where failures occur.

USE CASE 3

Improve reliability by adding automatic retries and detailed failure tracking to inter-service communication in a Kubernetes app.

Tech stack

GoRustKubernetes

Getting it running

Difficulty · hard Time to first run · 1h+

Requires a running Kubernetes cluster. Installation itself is fast but Kubernetes setup is a prerequisite.

Apache 2.0, use freely in personal and commercial projects. Modify and redistribute with attribution.

In plain English

Linkerd is a tool that installs into a Kubernetes cluster and automatically adds security, monitoring, and reliability features to the communication between your application's services, without requiring any changes to the application code itself. A service mesh is a dedicated layer of infrastructure that sits between your application components and manages how they talk to each other. Think of a modern web application as many small programs (called microservices) communicating over a network. Normally, each program would need its own code to handle things like encrypting that traffic, retrying failed requests, or tracking how fast each connection is. Linkerd moves all of that handling into a shared layer it manages itself. The security focus is central to Linkerd's design. It automatically encrypts all traffic between services using mutual TLS (a method where both sides of a connection verify each other's identity), without touching the application. It also provides detailed visibility into which services are talking to which, how long requests take, and where failures occur, through built-in metrics and dashboards. Linkerd is designed to be lightweight compared to other tools in this category. Its data-plane proxy component is written in Rust for low memory usage and fast performance. Installation into a Kubernetes cluster takes seconds via a command-line tool, and the getting started guide walks through the whole process. The project is part of the Cloud Native Computing Foundation, the organization that also oversees Kubernetes. It undergoes regular third-party security audits, and the results are published publicly in the repository. The license is Apache 2.0.

Copy-paste prompts

Prompt 1
Walk me through installing Linkerd into my Kubernetes cluster and verifying that mutual TLS encryption is active between two services.
Prompt 2
How do I use Linkerd to see a real-time dashboard of traffic between my Kubernetes microservices, including latency and error rates?
Prompt 3
I have a Kubernetes app with multiple microservices. Show me the steps to add Linkerd and confirm that all inter-service traffic is now encrypted.
Prompt 4
How does Linkerd's Rust-based proxy compare to Envoy in terms of memory usage and performance? I'm choosing a service mesh.
Open on GitHub → Explain another repo

← linkerd on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.