jaeger

jaeger manages the jaeger extension of Linkerd service mesh.

Flags

Flag	Usage
`--api-addr`	Override kubeconfig and communicate directly with the control plane at host:port (mostly for testing)
`--as`	Username to impersonate for Kubernetes operations
`--as-group`	Group to impersonate for Kubernetes operations
`--context`	Name of the kubeconfig context to use
`--kubeconfig`	Path to the kubeconfig file to use for CLI requests
`--linkerd-namespace` `-L`	Namespace in which Linkerd is installed
`--verbose`	Turn on debug logging

Subcommands

check

Check the Jaeger extension for potential problems.

The check command will perform a series of checks to validate that the Jaeger extension is configured correctly. If the command encounters a failure it will print additional information about the failure and exit with a non-zero exit code.

Examples

# Check that the Jaeger extension is up and running
linkerd jaeger check

Flags

Flag	Usage
`--namespace` `-n`	Namespace to use for –proxy checks (default: all namespaces)
`--output` `-o`	Output format. One of: table, json, short
`--proxy`	Also run data-plane checks, to determine if the data plane is healthy
`--wait`	Maximum allowed time for all tests to pass

dashboard

Open the Jaeger extension dashboard in a web browser

Flags

Flag	Usage
`--address`	The address at which to serve requests
`--port` `-p`	The local port on which to serve requests (when set to 0, a random port will be used)
`--show-url`	show only URL in the CLI, and do not open the browser
`--wait`	Wait for dashboard to become available if it’s not available when the command is run

install

Output Kubernetes resources to install jaeger extension.

Examples

# Default install.
linkerd jaeger install | kubectl apply -f -
# Install Jaeger extension into a non-default namespace.
linkerd jaeger install --namespace custom | kubectl apply -f -

The installation can be configured by using the --set, --values, --set-string and --set-file flags.
A full list of configurable values can be found at https://www.github.com/linkerd/linkerd2/tree/main/jaeger/charts/linkerd-jaeger/README.md

Flags

Flag	Usage
`--ignore-cluster`	Ignore the current Kubernetes cluster when checking for existing cluster configuration (default false)
`--registry`	Docker registry to pull jaeger-webhook image from ($LINKERD_DOCKER_REGISTRY)
`--set`	set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
`--set-file`	set values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
`--set-string`	set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
`--skip-checks`	Skip checks for linkerd core control-plane existence
`--values` `-f`	specify values in a YAML file or a URL (can specify multiple)
`--wait`	Wait for core control-plane components to be available

list

Lists which pods have tracing enabled

Flags

Flag	Usage
`--all-namespaces` `-A`	If present, list pods across all namespaces
`--namespace` `-n`	The namespace to list pods in

uninstall

Output Kubernetes resources to uninstall the Linkerd-jaeger extension.

This command provides all Kubernetes namespace-scoped and cluster-scoped resources (e.g services, deployments, RBACs, etc.) necessary to uninstall the Linkerd-jaeger extension.

Examples

linkerd uninstall | kubectl delete -f -