Jackett
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
Comparison · Infra & APIs
Pacemaker vs Gloo Gateway
A side-by-side editorial comparison of Pacemaker and Gloo Gateway — release velocity, themes, recent moves, and the top alternatives to consider.
Pacemaker vs Gloo Gateway: 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 Gloo Gateway?
One status-churn fix, shipped to four maintenance branches inside forty minutes.
Gloo maintains four release lines at once — 1.18, 1.19, 1.20 and 1.21 — plus a 1.22 beta series, and fixes are fanned across all of them together. On 5 August, v1.18.41, v1.19.20, v1.20.22 and v1.21.13 were cut within forty-five minutes of each other carrying the same Kubernetes Gateway report-churn fix and the same Go, gRPC and kubectl dependency bumps.
Pacemaker vs Gloo Gateway: 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.
Gloo Gateway
5.0INFRA · APIS
One status-churn fix, shipped to four maintenance branches inside forty minutes.
◆ Current state
Gloo maintains four release lines at once — 1.18, 1.19, 1.20 and 1.21 — plus a 1.22 beta series, and fixes are fanned across all of them together. On 5 August, v1.18.41, v1.19.20, v1.20.22 and v1.21.13 were cut within forty-five minutes of each other carrying the same Kubernetes Gateway report-churn fix and the same Go, gRPC and kubectl dependency bumps.
◆ Where it's heading
The recurring theme is translation correctness under Kubernetes Gateway API — specifically, bugs where the translator's internal state does not behave the way its callers assume. The report-churn fix found equality checks comparing maps of pointer values, so identical output registered as changed on every recompute. The delegateOptions fix in beta11 found RouteOptions assigned by reference from the snapshot, so merging parent Virtual Service options mutated shared protos and contaminated every other route for the rest of the cycle. Both ship with the same instinct for caution: the second one is gated behind GLOO_ISOLATE_DELEGATE_ROUTE_OPTIONS so operators can revert.
◆ Prediction
The 1.22 beta line will keep collecting Gateway API translation fixes ahead of a stable release, and each one that matters will be backported across all four maintenance branches on the same day, as this window shows twice.
Alternatives to Pacemaker and Gloo Gateway
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 Gloo Gateway.
Pressable
Ten days of bulk operations, then the AI assistant got the keys to multi-site access control.
Dependency-Track
A v5 release candidate train carrying a database migrator that has to work on the first try.
rsyslog
The syslog daemon is quietly becoming an OpenTelemetry-era pipeline, YAML config and all.
Contour
Three supported branches, patched in lockstep within the same minute.
HAProxy Kubernetes Ingress Controller
The changelog is a raw commit log, and its severity tags tell you more than the prose would.
See all Pacemaker alternatives → · See all Gloo Gateway alternatives →
Recent activity from Pacemaker and Gloo Gateway
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoGloo GatewayGloo 1.20.22 stops no-op Kubernetes Gateway report churn
- 2d agoGloo GatewayGloo 1.21.13 adds hostRewriteLiteral, reverts admission validation
- 2d agoGloo GatewayGloo 1.18.41 backports the Gateway report-churn fix
- 2d agoGloo GatewayGloo 1.19.20 backports the Gateway report-churn fix
- 5d agoGloo GatewayGloo 1.22.0-beta12 adds hostRewriteLiteral to shadowing
- 7d agoGloo GatewayGloo 1.22.0-beta11 isolates delegated RouteOptions before merging
- 11d agoPacemaker3.0.3: CVE-2026-10649 and remote message overflow fixes
- 28d agoPacemaker3.0.2: PSK auth for remote CIB operations
- 28d agoPacemaker3.0.1: TLS and X509 authentication for Pacemaker Remote ⚡
- 28d 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
Frequently asked questions
What is the difference between Pacemaker and Gloo Gateway?
They serve adjacent needs but don't currently overlap on shipped themes. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 5.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 Pacemaker better than Gloo Gateway?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 5.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 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 Gloo Gateway?
Top Gloo Gateway alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Gloo Gateway alternatives" section above for the current picks, or visit /alternatives/gloo for the full list with editorial commentary on each.