Getting started with Linkerd
If you’ve done anything in the Kubernetes space in recent years, you’ve most likely come across the words “Service Mesh”. It’s backed by a set of mature technologies that provides cross-cutting networking, security, infrastructure capabilities to be used by workloads running in Kubernetes in a manner that is transparent to the actual workload. This abstraction enables application developers to not worry about building in otherwise sophisticated capabilities for networking, routing, circuit-breaking and security, and simply rely on the services offered by the service mesh.
In this post, I’ll be covering?Linkerd, which is an alternative to?Istio. It has gone through a significant re-write when it transitioned from the JVM to a?Go-based Control Plane?and a?Rust-based Data Plane?a few years back and is now a part of the CNCF and is backed by Buoyant. It has proven itself widely for use in production workloads and has a healthy community and release cadence.
It achieves this with a side-car container that communicates with a Linkerd control plane that allows central management of policy, telemetry, mutual TLS, traffic routing, shaping, retries, load balancing, circuit-breaking and other cross-cutting concerns before the traffic hits the container. This has made the task of implementing the application services much simpler as it is managed by container orchestrator and service mesh. I covered Istio in a prior post a few years back, and much of the content is still applicable for this post,?if you’d like to have a look.
Adjunct Professor at IIT Bombay - Shailesh J. Mehta School of Management Dayananda Sagar University
2 年Your diagrams are unique ??
Vice President - Digital Transformation
2 年Anu!! Saw your posts after a Longtime, I rember those PSD2 days where you build the confluence page on how to set up the Teck Stacks and I read most of those contents and found so detail and was really helpful to the team. Good Job!!