openskills.info
Course catalog
Linkerd logoCourse Preview

Linkerd

Linkerd is a service mesh for Kubernetes. It places a small proxy beside selected workloads so you can observe, secure, and manage service-to-service traffic without changing application code.

itCloud native tools and technologies

Don't Panic: Linkerd

Linkerd is a Kubernetes service mesh, which means it puts a traffic-aware proxy beside selected workloads so that service calls acquire a shared set of eyes, locks, and guardrails. Before that, each application tended to carry its own client libraries, certificate handling, metrics, and policy habits. This works until several teams build several versions of the same precaution. Then the network becomes a group project, which is a known way to make everyone busy and nobody certain.

The useful picture is a pair of proxies around a service call. The outbound proxy sits next to the caller. The inbound proxy sits next to the destination. They handle the live connection, while the control plane, the in-cluster services that provide discovery, identity, and policy information, tells them how to behave. The command-line interface is a third surface for installing and inspecting the system. It is not secretly carrying traffic from a laptop, which is reassuring both technically and emotionally.

A meshed workload is a workload whose pod includes the Linkerd proxy. Installing the control plane does not transform every existing pod by administrative optimism. You enable injection for a namespace or workload, roll out new pods, inspect the resulting boundary, and then expand. Between meshed pods, mutual Transport Layer Security authenticates the proxies and encrypts the connection. It does not decide permission. That is the job of authorization policy, because knowing who knocked is not the same as deciding who gets in.

The surprise is that a proxy can be present without making every traffic question disappear. Recognized HTTP, HTTP version two, and gRPC traffic receives request-level views. Opaque TCP still passes through the proxy, but it has connection and byte-level visibility. A skip port passes around the proxy completely. Linkerd telemetry also cannot see application logic, database state, logs, or traces. The mesh is a traffic boundary, not an all-seeing ceiling panel.

Read the Intro for the architecture and the security boundary. Use Slides when the control plane, data plane, and traffic classes need a compact map. Keep the Cheatsheet nearby for policy resources, observability commands, reliability controls, and production checks. Field Notes is the brisk version of what becomes operationally expensive after a friendly demo. The Quiz then checks whether the terms have stopped looking like a bowl of carefully encrypted alphabet soup.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources