Automatic Proxy Injection

    See Adding Your Service for a walkthrough of how to use this feature in practice.

    Note

    Proxy injection is implemented as a . This means that the proxies are added to pods within the Kubernetes cluster itself, regardless of whether the pods are created by kubectl, a CI/CD system, or any other system.

    For each pod, two containers are injected:

    1. linkerd-proxy, the Linkerd data plane proxy itself.

    Automatic injection can be disabled for a pod or deployment for which it would otherwise be enabled, by adding the annotation.

    The linkerd inject CLI command is a text transform that, by default, simply adds the inject annotation to a given Kubernetes manifest.

    See the for more information.