Hello Linkerd fans!
This edge release introduces experimental support for distributed tracing as
well as a redesigned sidebar in the Web UI!
Experimental support for distributed tracing means that Linkerd data plane
proxies can now emit trace spans, allowing you to see the exact amount of time
spent in the Linkerd proxy for traced requests. The new
`config.alpha.linkerd.io/trace-collector-service-account` tracing annotations
allow specifying which pods should emit trace spans.
The goal of the dashboard's sidebar redesign was to reduce load on Prometheus
and simplify navigation by providing top-level views centered around namespaces
- Introduced a new `--cluster-domain` flag to the `linkerd install` command that allows setting a custom cluster domain (thanks @arminbuerkle!)
- Fixed the `linkerd endpoints` command to use the correct Destination API address (thanks @Pothulapati!)
- Added `--disable-heartbeat` flag for `linkerd` `install|upgrade` commands
- Instrumented the proxy-injector to provide additional metrics about injection (thanks @Pothulapati!)
- Added support for `config.linkerd.io/admission-webhooks: disabled` label on namespaces so that the pod's creation events in these namespaces are ignored by the proxy injector; this fixes connection errors between the k8s API Server and the control plane, when all the proxy injector replicas are unavailable (thanks @hasheddan!)
- Introduced `config.linkerd.io/trace-collector` and `config.alpha.linkerd.io/trace-collector-service-account` pod spec annotations to support per-pod tracing
- Web UI
- Workloads are now viewed by namespace, with an "All Namespaces" option, to improve dashboard performance
- Added experimental distributed tracing support
As always, we're excited to hear your feedback. Please try the new release and
send questions/comments to this mailing list, and report bugs via GitHub.