Insomnia
Insomnia's current work is Git, Cloud Sync and gRPC ergonomics — not headline features.
Comparison · Infra & APIs
Pacemaker vs kOps
A side-by-side editorial comparison of Pacemaker and kOps — release velocity, themes, recent moves, and the top alternatives to consider.
Pacemaker vs kOps: at a glance
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.
What is kOps?
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
kOps publishes alpha and beta tags rather than finals to this feed, with long commit lists dominated by provider-specific work. The 1.36 cycle removed Amazon Linux 2 support outright and changed omitted authorization to default to RBAC instead of AlwaysAllow. The 1.37 alpha continues along provider lines: Azure node identity now uses the IMDS attested metadata document, AWS reconciles target group health check changes on existing groups, GCE does the same for HTTP health checks, and Linode gained SSH key management.
Pacemaker vs kOps: editorial side-by-side
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.
kOps
2.5INFRA · APIS
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
◆ Current state
kOps publishes alpha and beta tags rather than finals to this feed, with long commit lists dominated by provider-specific work. The 1.36 cycle removed Amazon Linux 2 support outright and changed omitted authorization to default to RBAC instead of AlwaysAllow. The 1.37 alpha continues along provider lines: Azure node identity now uses the IMDS attested metadata document, AWS reconciles target group health check changes on existing groups, GCE does the same for HTTP health checks, and Linode gained SSH key management.
◆ Where it's heading
Two patterns run through these tags. The first is reconciliation — kOps is closing the gaps where it created a resource but never re-checked it, which is what turns a provisioning tool into something that can be run continuously. The second is deliberate narrowing: dropping Amazon Linux 2 and defaulting authorization to RBAC both trade compatibility for a safer, smaller supported matrix.
◆ Prediction
The health check reconciliation pattern has now landed for AWS and GCE in the same cycle, so Azure and the smaller providers are the likely next targets.
Alternatives to Pacemaker and kOps
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 Pacemaker or kOps.
Headlamp
Headlamp's feed is mostly chart bumps; the plugin toolchain is where the actual work shows.
Kubeshark
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
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 Pacemaker alternatives → · See all kOps alternatives →
Recent activity from Pacemaker and kOps
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoPacemaker3.0.3: CVE-2026-10649 and remote message overflow fixes
- 25d agokOpsAzure attested node identity; AWS and GCE health check reconcile
- 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
- 1mo agokOpsOmitted authorization now defaults to RBAC instead of AlwaysAllow
- 2mo agokOpsAmazon Linux 2 support removed; warm pools take user-defined images
Frequently asked questions
What is the difference between Pacemaker and kOps?
They serve adjacent needs but don't currently overlap on shipped themes. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Pacemaker better than kOps?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 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.
What are the best alternatives to kOps?
Top kOps alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "kOps alternatives" section above for the current picks, or visit /alternatives/kops for the full list with editorial commentary on each.