Linkerd dashboard

v1.0.0

November 17, 2026

Linkerd dashboard v1.0.0 adds login, Live calls for watching requests as they happen, and OSCAL compliance reporting.

Breaking changes

Login is now required by default

To provide enterprise-level security, the dashboard now asks users to log in with a Kubernetes bearer token.

Who is affected

Anyone who uses the dashboard.

What you need to do

Get a token and log in, as described in Logging in to the dashboard. The OSCAL endpoint is the exception; see below.

The chart creates a Service and Linkerd authorization policy resources

The Helm chart now creates a linkerd-dashboard Service, and a Linkerd Server, HTTPRoutes, and AuthorizationPolicy resources for the dashboard.

Who is affected

Anyone who upgrades the dashboard. In particular, anyone who created a Service named linkerd-dashboard by hand, for example to reach the dashboard from inside the cluster.

What you need to do

  • Don’t create an AuthorizationPolicy that targets the dashboard’s Server or namespace.

New features

Live calls

Live calls stream a sample of live requests for a namespace, all resources of one type, or a single workload or pod. You can group or filter requests, and share a view by copying its URL. Live calls are also available on each resource’s detail page.

Live calls stream requests from the Linkerd proxies directly, and don’t use the Linkerd viz extension. The dashboard names itself as the proxies’ tap client when meshed pods are created, and its install fails while the viz extension is present; see Enabling Live calls. To stop Live calls for a namespace or workload, set its tap.buoyant.io/enabled annotation to false. The viz extension’s viz.linkerd.io/disable-tap annotation isn’t read. To include HTTP headers in request details, set the dashboard’s tapHeadersEnabled value.

As of enterprise-2.20.6 additional guardrails for Live calls are available. See proxy annotations for more details.

Live calls will work with previous versions, however some care must be taken when using this capability.

OSCAL compliance reporting

The new /api/oscal/assessment-results endpoint exports the mesh’s mTLS (sc-8) and FIPS (sc-13) status as an OSCAL Assessment Results document, tagged with the FedRAMP 20x indicator KSI-SVC-SIN.

The endpoint doesn’t use dashboard login. Instead, Linkerd policy allows only the meshed service accounts listed in the new oscal.authorizedServiceAccounts value, and denies all others by default. See Exporting OSCAL assessment results and the OSCAL assessment results reference.

Fine-grained changelog

  • Add a login page that validates Kubernetes bearer tokens. Sessions end after 20 minutes of inactivity or when the token expires.
  • Add the authPolicy Helm value to turn off login
  • Add the tapHeadersEnabled Helm value to include HTTP headers in Live calls
  • Add the oscal.authorizedServiceAccounts Helm value to authorize OSCAL endpoint clients
  • Read dashboard settings from the linkerd-dashboard ConfigMap in the dashboard’s namespace, with a Role that allows the dashboard to read it
  • Allow the dashboard to create tokenreviews in its Helm chart ClusterRole
  • Create a linkerd-dashboard Service and Linkerd policy resources for the dashboard’s http port
  • Add the Live calls page, with grouped and ungrouped views, filtering, and request details
  • Stream Live calls from the Linkerd proxies directly, without the viz extension, and reconnect when a proxy ends a stream at its tap.buoyant.io/max-lifetime
  • Add a tap-injector webhook to the dashboard, configured by the tapInjector.* Helm values, which sets the dashboard’s identity on meshed pods’ proxies and honors the tap.buoyant.io/enabled annotation. The dashboard won’t install while the viz extension’s tap-injector is present
  • Restart the dashboard when helm upgrade changes its ConfigMap, so authPolicy and tapHeadersEnabled take effect without a manual restart
  • Split resource detail pages into Overview, Metrics, Edges, and Live calls tabs
  • Add the OSCAL assessment results endpoint, authorized by Linkerd policy, with an access log entry for every request it receives
  • Accept plain text in table filters