Insomnia
Insomnia's current work is Git, Cloud Sync and gRPC ergonomics — not headline features.
Comparison · Infra & APIs
Kubeshark vs Pacemaker
A side-by-side editorial comparison of Kubeshark and Pacemaker — release velocity, themes, recent moves, and the top alternatives to consider.
Kubeshark vs Pacemaker: at a glance
What is Kubeshark?
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
Kubeshark is mid-transition from V1 to V2, announced for January 2026. The v52.11.0 release rewrote the backend entirely — V2 runs on the new implementation while V1 stays on the legacy one — and added cluster-wide L4 PCAP export plus L7-to-L4 mapping that ties API calls back to the TCP and UDP connections carrying them. Since then the releases have been smaller: connectivity map performance, per-flow PCAP files in snapshot archives, and a migration of every service domain from kubehq.com to kubeshark.com.
What is Pacemaker?
Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.
Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.
Kubeshark vs Pacemaker: editorial side-by-side
Kubeshark
0.0INFRA · APIS
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
◆ Current state
Kubeshark is mid-transition from V1 to V2, announced for January 2026. The v52.11.0 release rewrote the backend entirely — V2 runs on the new implementation while V1 stays on the legacy one — and added cluster-wide L4 PCAP export plus L7-to-L4 mapping that ties API calls back to the TCP and UDP connections carrying them. Since then the releases have been smaller: connectivity map performance, per-flow PCAP files in snapshot archives, and a migration of every service domain from kubehq.com to kubeshark.com.
◆ Where it's heading
The product is moving down the stack. It started as an API-level traffic viewer and the recent work is all about L4 — connectivity maps, raw PCAP export, mapping L7 calls onto the connections beneath them — which puts it closer to a cluster-wide packet capture tool than a service-mesh observability dashboard. The licensing is moving in the opposite direction of the feature set: an almost-unlimited complimentary licence through the end of 2025 was replaced by one capped at 100 nodes, so the free tier is being defined rather than left open. Two releases also mention agentic infrastructure being staged but not yet usable.
◆ Prediction
Expect V2 to consolidate onto the new backend and the legacy V1 path to be dropped once the transition completes, since the release notes already describe V1 as being sunset. The staged agentic infrastructure is the most likely candidate for the next substantive feature, given it has been shipped inert twice.
Pacemaker
6.3INFRA · APIS
Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.
◆ Current state
Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.
◆ Where it's heading
The cluster's internal transport is being rebuilt on the assumption that the network between nodes is not trusted. Authentication and encryption arrived first, and the fixes that followed, overflow guards and a maximum remote message size, are the hardening pass on the same code paths. Release discipline is heavy and visible: each version ships a release candidate with an identical commit set days earlier, and every 3.0 release documents the regressions it introduced and where they were fixed.
◆ Prediction
Remote CIB operations now support both X509 certificates and PSK, and the recent fixes all sit in message framing and size limits; further work is most likely to continue in that message-handling code rather than adding another authentication mechanism.
Alternatives to Kubeshark and Pacemaker
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Kubeshark or Pacemaker.
kOps
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
Headlamp
Headlamp's feed is mostly chart bumps; the plugin toolchain is where the actual work shows.
Certbot
Certbot is rebuilding its API around identifiers so certificates aren't only for domain names.
electerm
electerm now ships its own free AI backend, turning a terminal client into an assistant surface.
Apptainer
Apptainer 1.5 adds CDI device support and builds SIF images straight from Dockerfiles.
See all Kubeshark alternatives → · See all Pacemaker alternatives →
Recent activity from Kubeshark and Pacemaker
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoPacemaker3.0.3: CVE-2026-10649 and remote message overflow fixes
- 29d agoPacemaker3.0.2: PSK auth for remote CIB operations
- 29d agoPacemaker3.0.1: TLS and X509 authentication for Pacemaker Remote ⚡
- 29d agoPacemaker3.0.3-rc1: release candidate for the CVE fix set
- 1mo agoPacemaker2.1.11: CVE-2026-10649 backported to the maintenance branch
- 1mo agoPacemaker2.1.11-rc1: release candidate for the 2.1 CVE backport
- 6mo agoKubesharkv52.12.0 moves every service domain to kubeshark.com
- 6mo agoKubesharkComplimentary licence is redefined as free up to 100 nodes
- 7mo agoKubesharkBackend fully rewritten for V2, with L7-to-L4 traffic mapping ⚡
- 8mo agoKubesharkNear-unlimited complimentary licence bundled into the Helm chart
Frequently asked questions
What is the difference between Kubeshark and Pacemaker?
They serve adjacent needs but don't currently overlap on shipped themes. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Kubeshark better than Pacemaker?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Kubeshark?
Top Kubeshark alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Kubeshark alternatives" section above for the current picks, or visit /alternatives/kubeshark for the full list with editorial commentary on each.
What are the best alternatives to Pacemaker?
Top Pacemaker alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Pacemaker alternatives" section above for the current picks, or visit /alternatives/pacemaker for the full list with editorial commentary on each.