← Back to home
Comparison · Infra & APIs

Gloo Gateway vs Kubeshark

A side-by-side editorial comparison of Gloo Gateway and Kubeshark — release velocity, themes, recent moves, and the top alternatives to consider.

Gloo Gateway vs Kubeshark: at a glance

FeatureGloo GatewayKubeshark
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themesapi-gateway, kubernetes-gateway-api, multi-branch-backports, envoykubernetes, network-observability, packet-capture, ebpf
Last editorial update1d ago2h ago
WebsiteVisit →Visit →

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.

Read the full Gloo Gateway trajectory →

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.

Read the full Kubeshark trajectory →

Gloo Gateway vs Kubeshark: editorial side-by-side

G
Gloo Gateway
INFRA · APIS
5.0

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.

K
Kubeshark
INFRA · APIS
0.0

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.

Alternatives to Gloo Gateway and Kubeshark

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 Gloo Gateway or Kubeshark.

See all Gloo Gateway alternatives → · See all Kubeshark alternatives →

Recent activity from Gloo Gateway and Kubeshark

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3d agoGloo GatewayGloo 1.20.22 stops no-op Kubernetes Gateway report churn
  2. 3d agoGloo GatewayGloo 1.21.13 adds hostRewriteLiteral, reverts admission validation
  3. 3d agoGloo GatewayGloo 1.18.41 backports the Gateway report-churn fix
  4. 3d agoGloo GatewayGloo 1.19.20 backports the Gateway report-churn fix
  5. 6d agoGloo GatewayGloo 1.22.0-beta12 adds hostRewriteLiteral to shadowing
  6. 8d agoGloo GatewayGloo 1.22.0-beta11 isolates delegated RouteOptions before merging
  7. 6mo agoKubesharkv52.12.0 moves every service domain to kubeshark.com
  8. 6mo agoKubesharkComplimentary licence is redefined as free up to 100 nodes
  9. 7mo agoKubesharkBackend fully rewritten for V2, with L7-to-L4 traffic mapping
  10. 8mo agoKubesharkNear-unlimited complimentary licence bundled into the Helm chart

Frequently asked questions

What is the difference between Gloo Gateway and Kubeshark?

They serve adjacent needs but don't currently overlap on shipped themes. Gloo Gateway is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Gloo Gateway better than Kubeshark?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Gloo Gateway is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 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.

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.