kOps
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
A side-by-side editorial comparison of OpenKruise and Gloo Gateway — release velocity, themes, recent moves, and the top alternatives to consider.
Seven workload APIs graduated to beta — then the feed went quiet for six months.
OpenKruise's tracked releases stop in January 2026, all of them alphas of v1.9.0. The substantive one moved seven APIs — BroadcastJob, AdvancedCronJob, ImagePullJob, ImageListPullJob, NodeImage, Advanced DaemonSet and SidecarSet — from v1alpha1 to v1beta1, updated the Kubernetes dependency to 1.32.6 and Go to 1.23, and added capability across the workload controllers: reserved unschedulable pods in UnitedDeployment, cron-driven ImagePullJob, deadline handling in CloneSet, and PodUnavailableBudget protection for pod resize. Two of the three entries are the same changelog tagged four minutes apart.
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.
OpenKruise's tracked releases stop in January 2026, all of them alphas of v1.9.0. The substantive one moved seven APIs — BroadcastJob, AdvancedCronJob, ImagePullJob, ImageListPullJob, NodeImage, Advanced DaemonSet and SidecarSet — from v1alpha1 to v1beta1, updated the Kubernetes dependency to 1.32.6 and Go to 1.23, and added capability across the workload controllers: reserved unschedulable pods in UnitedDeployment, cron-driven ImagePullJob, deadline handling in CloneSet, and PodUnavailableBudget protection for pod resize. Two of the three entries are the same changelog tagged four minutes apart.
This is a project consolidating rather than expanding — graduating APIs to beta is a commitment to stop changing their shape, and the accompanying features fill gaps in existing controllers rather than adding new ones. The pod resize protection is the one forward-looking item, tracking in-place resource resizing as it stabilizes upstream in Kubernetes. Whether the v1.9.0 line ever reached a stable release is not visible here.
The obvious next step is a stable v1.9.0 with the v1beta1 APIs finalized. The six-month gap since the last alpha is worth verifying against the project's actual release activity before reading it as a slowdown.
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.
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.
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.
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 OpenKruise or Gloo Gateway.
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
Headlamp's feed is mostly chart bumps; the plugin toolchain is where the actual work shows.
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
Certbot is rebuilding its API around identifiers so certificates aren't only for domain names.
electerm now ships its own free AI backend, turning a terminal client into an assistant surface.
Apptainer 1.5 adds CDI device support and builds SIF images straight from Dockerfiles.
See all OpenKruise alternatives → · See all Gloo Gateway alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top OpenKruise alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "OpenKruise alternatives" section above for the current picks, or visit /alternatives/openkruise for the full list with editorial commentary on each.
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.