Enabling Add-Ons

Add-On’s in Linkerd are optional and configurable. A configuration file is passed to the install operation (available both through Helm and CLI). This config is also stored as a configmap called , allowing upgrades to work seamlessly without having user to pass the config file again. Configuration can be updated during upgrades.

Note

Add-On’s are available in Linkerd starting from version edge-20.2.3.

You can find the list of add-ons present in the .

Other Add-On’s would also have a similar installation approach.

The following is the Add-On configuration file, that will be passed to installation. Here we configure the Tracing Add-On to be enabled, and also overwrite the trace collector’s resources. If values are not overwritten, The default values will be used.

The same configuration file can be used both through the CLI and Helm.

linkerd CLI now supports a flag, which is used to pass the confiugration of add-ons. Now, the above configuration file can be passed as

Now, we pass the add-on configuration file to the helm install command.

First, you should also see two new components be installed i.e linkerd-collector and linkerd-jaeger.

Now, The control-plane components traces, along with the linkerd-proxy traces are sent to the , which are then sent to the linkerd-jaeger. These Traces can be viewed in the jaeger UI by port-forwarding the service as

Traces from the control-plane components can be viewed at localhost:16886