Essential Linkerd CLI Commands and Flags Explained
This article provides a concise reference of the most frequently used Linkerd CLI commands and their associated flags, detailing how each command interacts with the control plane, injects proxies, and offers diagnostic and management capabilities for Kubernetes service meshes.
Linkerd CLI is the primary interface for interacting with a Linkerd service mesh. It can install the control plane into a Kubernetes cluster, inject the Linkerd proxy into services, and expose detailed metrics about service performance.
Common Linkerd CLI Commands
authz : List server authorizations for resources.
check : Verify the Linkerd installation for potential issues.
completion : Output shell completion code for bash, zsh, or fish.
diagnostics : Run diagnostics on Linkerd components.
identity : Show certificates for one or more selected pods.
inject : Add the Linkerd proxy to Kubernetes manifests.
install : Generate Kubernetes manifests to install Linkerd.
install-cni : Generate manifests to install the Linkerd CNI plugin.
jaeger : Manage the Jaeger extension for Linkerd service mesh.
multicluster : Manage multi‑cluster configurations for Linkerd.
profile : Output the service profile configuration for a Kubernetes service.
repair : Re‑create the secret/linkerd-config-overrides if it has been deleted.
uninject : Remove the Linkerd proxy from Kubernetes manifests.
uninstall : Output resources needed to uninstall the Linkerd control plane.
upgrade : Generate manifests to upgrade an existing Linkerd control plane.
version : Print client and server version information.
viz : Manage the Linkerd Viz extension for visualizing the service mesh.
Common Flags Available to All Commands
--api-addr : Override kubeconfig and communicate directly with the control plane at host:port (mainly for testing).
--context : Name of the kubeconfig context to use.
--help, -h : Show help for the Linkerd command.
--kubeconfig : Path to the kubeconfig file used for CLI requests.
--linkerd-namespace, -l : Namespace where Linkerd is installed (default $LINKERD_NAMESPACE).
--verbose : Enable debug logging.
--as : Simulated username for Kubernetes operations.
These commands and flags together enable administrators and developers to install, configure, diagnose, and upgrade Linkerd deployments directly from the command line.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.