Loading content
Linkerd is a lightweight, CNCF-hosted service mesh for Kubernetes that provides observability, reliability and secure communication via mTLS. It runs as small control and data plane components, focusing on simplicity, low overhead and production readiness. Useful for traffic shifting, retries, and telemetry collection.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
Linkerd is a lightweight service mesh for Kubernetes that provides encrypted connections, routing, reliability, and telemetry through transparent proxies.
Linkerd emerged at Buoyant in 2015 from the problem of controlling microservice network behavior independently of application code. Its development moved from a general service-mesh proxy toward a Kubernetes-focused, resource-conscious architecture.
Each relevant workload gets a small proxy beside its container. The proxy handles network policy and measurement while a control plane distributes policy and identity information. The application keeps speaking its protocol as Linkerd secures and observes traffic between proxies.
It mediates a workload's traffic and implements mesh capabilities.
It enables mutual authentication between services.
It controls or limits which services may communicate.
Linkerd fits Kubernetes environments that need consistent encryption, service metrics, or controlled routing. Extra proxies add resource use, operational knowledge, and another troubleshooting layer.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.