The Consolidated Kubernetes Service Mesh Linkerd Config

Eliza Weisman

Eliza Weisman
August 4, 2017 • 3 min read

A Service Mesh for Kubernetes

Since October 2016, we’ve provided the popular “A Service Mesh for Kubernetes” series of blog posts, highlighting major features of Linkerd and providing working examples of Linkerd and Kubernetes configurations to make use of them. These posts are a useful way to explore various Linkerd features and use-cases in depth.

Now we’ve compressed the configuration in the series into a single, consolidated config to act as a canonical starting point for adding the Linkerd service mesh to a Kubernetes cluster. In this post, we’ll talk you through the details of this configuration file. If you just want to get started with it, you can download it here: Linkerd Kubernetes Service Mesh config file.

A Kubernetes for the Service Mesh

Many Linkerd users have started with the config files in the “A Service Mesh for Kubernetes” series. This is great, and we’d like to encourage the continued use of these blog posts as an educational resource. However, the configs in these blog posts are intended to demonstrate specific Linkerd features in a self-contained manner. Assembling a fully-featured, production-ready configuration requires stitching together several different configs, and this can be difficult!

The consolidated Linkerd Kubernetes config merges the configurations across all these posts and provides a complete configuration to deploy a service mesh of Linkerd instances onto your cluster as a Kubernetes DaemonSet. This configuration provides support for HTTP, HTTP/2, and gRPC calls, as well as  load balancing, circuit breaking, dynamic routing, and ingress and egress control.

Once deployed, HTTP applications can use Linkerd by setting the http_proxy environment variable to  $(NODE_NAME):4140, where NODE_NAME is the name of the Kubernetes node where the application instance is running. Ingress traffic sent to port 80 (or port 8080 for HTTP/2) on the ingress address of the cluster will be routed according to the Kubernetes Ingress resource, and any egress requests to names that do not correspond to Kubernetes services (e.g. “”) will fall back to a DNS lookup and be proxied outside the cluster.

Deploying the Service Mesh

To deploy the service mesh onto your cluster, simply run the following commands:

kubectl create ns linkerd
kubectl apply -f

To verify that Linkerd is running, run:

kubectl -n linkerd port-forward $(kubectl -n linkerd get pod -l app=l5d -o jsonpath='{.items[0]}') 9990 &

And then open http://localhost:9990 in your web browser – you should see the Linkerd administration dashboard.

More instructions on configuring your application to work with the official Kubernetes config can be found in the Linkerd documentation.


With this config, it’s easier than ever to get started running Linkerd on Kubernetes! Whether you’re running Kubernetes on a massive production cluster or in Minikube on your laptop; whether you’re already using Linkerd to route critical production traffic or just checking it out for the first time, this config will allow you to easily set up a fully-featured Linkerd service mesh, and serve as a starting point to write your own custom configurations to best suit the needs of your application.

For more information about Linkerd’s various features on Kubernetes, see our Service Mesh For Kubernetes blog series. As always, if you have any questions or just want to chat about Linkerd, join the Linkerd Slack or browse the Linkerd Support Forum for more in-depth discussion.

Suggested Blog Posts