Linkerd vs Grafana
Side-by-side trajectory, velocity, and editorial themes.
Linkerd coasts on its 2.19 post-quantum release while filling the gap with technical blog content.
Linkerd's stable cadence has slowed: the last named release is 2.19 from October 2025, which made post-quantum key exchange the default TLS mode. Since then, the team has leaned on edge-release roundups and community blog posts — deep dives into linkerd-destination, protocol detection, certificate rotation, and how Kubernetes native sidecars interact with mesh shutdown semantics — rather than feature-stamped stable releases.
The project is in mature-maintenance posture. Edge releases keep code moving, but the messaging is shifting toward operational guidance (cert rotation, native sidecars, OTel integration) rather than new mesh capabilities. The next strategic question is whether 2.20 lands a directional feature or whether Linkerd keeps positioning as the lightweight, predictable alternative to Istio's growing surface area.
Expect the next named release to formalize Kubernetes native sidecar support as the recommended deployment mode, and OpenTelemetry-based metrics to graduate from edge into stable.
Grafana ships fleet-wide CVE patches across five branches while Dynamic Dashboards anchor the new 13.0 line.
Grafana is on a brisk monthly minor cadence — 12.2, 12.3, 12.4, and 13.0 all landed between late March and mid-April, with 13.0 making Dynamic Dashboards GA as the new dashboarding primitive. Today they cut a coordinated security release across every supported branch (11.6, 12.2, 12.3, 12.4, 13.0) patching the same set of around ten CVEs. The dual pattern — fast feature iteration on top, broad LTS coverage underneath — is intact.
The platform is consolidating around Dynamic Dashboards as the default authoring model and pushing Git-driven workflows (Git Sync, templates, shared queries) into the everyday loop. Logs and Drilldown experiences keep getting structural rewrites rather than cosmetic polish, suggesting Grafana sees the exploration UX as the differentiation lever against newer observability vendors. Maintenance discipline is a feature here, not background work: synchronized multi-branch CVE releases keep enterprise customers on a buyable upgrade path.
Expect a 13.1 minor inside the next month continuing on Dynamic Dashboards, Git Sync, and Drilldown threads, plus follow-up patch releases as the post-disclosure window for these CVEs closes. A public write-up explaining the ten-CVE batch is likely if any of the bugs turn out to be remotely exploitable.
See more alternatives to Linkerd →
See more alternatives to Grafana →