Feb 21, 2024: Announcing Linkerd 2.15 with support for VM workloads, native sidecars, and SPIFFE! Read more »

This is not the latest version of Linkerd!
This documentation is for Linkerd 1.x, an older version with some significant differences. You may want to see the Linkerd 2.x (current) documentation instead.

Transparent Proxying

If you’re running in Kubernetes, you can use the linkerd-inject utility to transparently proxy requests through a Daemonset Linkerd. This script runs an initContainer in each pod that sets up iptables rules on each pod to forward traffic to the Linkerd running on the node. Note that this setup proxies all outbound traffic to a single Linkerd port, so it won’t work if you are using multiple protocols.

To use linkerd-inject:

# install linkerd-inject
$ go get github.com/linkerd/linkerd-inject

# inject init container and deploy this config
$ kubectl apply -f <(linkerd-inject -f <your k8s config>.yml -linkerdPort 4140)

Note that in minikube, you need the -useServiceVip flag.

If you don’t want to use a script to modify your configs, you could insert the following initContainer spec into your configs manually:

- name: init-linkerd
  image: linkerd/istio-init:v1
  - name: NODE_NAME
        fieldPath: spec.nodeName
    - -p
    - "4140" # port of the Daemonset Linkerd's incoming router
    - -s
    - "L5D" # Linkerd Daemonset service name, uppercased
    - -m
    - "false" # set to true if running in minikube
  imagePullPolicy: IfNotPresent
      - NET_ADMIN

Non Kubernetes Environments

The prepare-proxy.sh script which sets up the iptables rules assumes you are running in Kubernetes, (and that you are running a Daemonset Linkerd) but it is possible to set up iptables rules to transparently proxy requests in other environments. If you’re running one Linkerd per host, looking at the OUTPUT chain rules in that file should get you started.