Add your service to the mesh by marking it for data plane proxy injection.
Reduce deployment risk by combining Linkerd and Flagger to automate canary releases based on service metrics.
Configure Linkerd to retry outgoing requests on failure.
Configure how long Linkerd will wait before failing an outgoing request.
Modify the Linkerd Installation
Linkerd makes it easy to debug a failing application. Check out how to do it yourself with Emojivoto.
Try out some of Linkerd's features, such as per-route metrics with a demo application.
Use Linkerd to help instrument your application with distributed tracing.
Integrate Linkerd's Prometheus with your existing metrics infrastructure.
Make it easy for others to access Linkerd and Grafana dashboards without the CLI.
Generate your own mTLS root certificate instead of letting Linkerd do it for you.
Configure per-route metrics for your application.
Practice chaos engineering by injecting faults into services with Linkerd.
Install Linkerd to your own Kubernetes cluster.
Install Linkerd onto your own Kubernetes cluster using Helm.
Linkerd proxy log levels can be modified dynamically to assist with debugging.
RBAC best practices for your Linkerd installation.
Linkerd encrypts your service's traffic by default.
Create a service profile that provides more details for Linkerd to build on.
Troubleshoot issues with your Linkerd installation.
Linkerd can be easily removed from a Kubernetes cluster.
Upgrade Linkerd to the latest version.
Use Linkerd with a custom cluster domain.
Use debugging endpoints provided by the control plane components.
Linkerd works alongside your ingress controller of choice.
Use Linkerd with a pod security policy enabled.
Inject the debug container to capture network packets.