Tasks

Adding Your Services to Linkerd. In order for your services to take advantage of Linkerd, they also need to be meshed by injecting Linkerd’s data plane proxy into their pods.

. Reduce deployment risk by combining Linkerd and Flagger to automate canary releases based on service metrics.

Automatically Rotating Control Plane TLS Credentials. Use cert-manager to automatically rotate control plane TLS credentials.

. Use cert-manager to automatically rotate webhook TLS credentials.

Bringing your own Prometheus. Use an existing Prometheus instance with Linkerd.

. Limit the Linkerd proxy’s CPU usage.

Configuring Retries. Configure Linkerd to automatically retry failing requests.

. Configure Linkerd to automatically fail requests that take too long.

Control Plane Debug Endpoints. Linkerd’s control plane components provide debug endpoints.

. Use Kustomize to modify Linkerd’s configuration in a programmatic way.

Debugging 502s. Determine why Linkerd is returning 502 responses.

. Follow a long-form example of debugging a failing gRPC application using live request tracing.

Debugging HTTP applications with per-route metrics. Follow a long-form example of debugging a failing HTTP application using per-route metrics.

. Use Linkerd to help instrument your application with distributed tracing.

Exporting Metrics. Integrate Linkerd’s Prometheus with your existing metrics infrastructure.

. Generate your own mTLS root certificate instead of letting Linkerd do it for you.

Getting Per-Route Metrics. Configure per-route metrics for your application.

. Use Linkerd SMI extension to work with Service Mesh Interface(SMI) resources.

Graceful Pod Shutdown. Gracefully handle pod shutdown signal.

. Linkerd works alongside your ingress controller of choice.

Injecting Faults. Practice chaos engineering by injecting faults into services with Linkerd.

. Install Linkerd to your own Kubernetes cluster.

Installing Linkerd with Helm. Install Linkerd onto your own Kubernetes cluster using Helm.

. Allow Linkerd to manage cross-cluster communication.

Linkerd and Pod Security Policies (PSP). Using Linkerd with a pod security policies enabled.

. Update Linkerd’s TLS trust anchor and issuer certificate.

Modifying the Proxy Log Level. Linkerd proxy log levels can be modified dynamically to assist with debugging.

. Allow Linkerd to manage cross-cluster communication.

Multi-cluster communication with StatefulSets. cross-cluster communication to and from headless services.

. Follow this workflow if any of your TLS certs have expired.

Rotating webhooks certificates. Follow these steps to rotate your Linkerd webhooks certificates.

. Best practices for securing your Linkerd installation.

Setting Up Service Profiles. Create a service profile that provides more details for Linkerd to build on.

. Troubleshoot issues with your Linkerd installation.

Uninstalling Linkerd. Linkerd can be easily removed from a Kubernetes cluster.

. Unlink and uninstall Linkerd multicluster.

Upgrading Linkerd. Upgrade Linkerd to the latest version.

. Upgrading Multicluster to Linkerd 2.9.

Upgrading to Linkerd 2.10: ports and protocols. Upgrading to Linkerd 2.10 and handling skip-ports, server-speaks-first protocols, and more.

. Use Linkerd with a custom cluster domain.

Using A Private Docker Repository. Using Linkerd with a Private Docker Repository.

. Add functionality to Linkerd with optional extensions.

Using GitOps with Linkerd with Argo CD. Use Argo CD to manage Linkerd installation and upgrade lifecycle.

. Inject the debug container to capture network packets.

Validating your mTLS traffic. You can validate whether or not your traffic is being mTLS’d by Linkerd.