Apptainer
Apptainer 1.6 candidate adds delta images that rebuild only what changed.
A side-by-side editorial comparison of Argo Rollouts and Gloo Gateway — release velocity, themes, recent moves, and the top alternatives to consider.
An RC-only feed where 1.9's headline change was reverted before it shipped.
Every entry in this window is a release candidate; no GA tag appears at all. The 1.9 line spent three RCs largely on pipeline problems — rc3 explicitly ships no changes from rc2 — and its one architectural change was withdrawn. That change would have narrowed .status.selector to report only the stable ReplicaSet for traffic-routed canaries so HPA stopped counting canary pods in its desired-replica math. The 1.10.0-rc1 notes are dominated by build and dependency work.
Gloo Gateway 1.20.29 stops a failed restart from wiping every Envoy's config
Gloo Gateway keeps maintaining 1.19, 1.20 and 1.21 in parallel. The 1.20.29 release fixes a failure where, after a gloo restart, a failed first reconcile sent every connected Envoy an empty config; it also keeps the in-memory Proxy store across setup re-runs and delays setup restarts until the first xDS sync. The 21 October batch had fixed proxies stuck on stale endpoints.
Every entry in this window is a release candidate; no GA tag appears at all. The 1.9 line spent three RCs largely on pipeline problems — rc3 explicitly ships no changes from rc2 — and its one architectural change was withdrawn. That change would have narrowed .status.selector to report only the stable ReplicaSet for traffic-routed canaries so HPA stopped counting canary pods in its desired-replica math. The 1.10.0-rc1 notes are dominated by build and dependency work.
The visible direction is operational rather than behavioural: notifications broadened to Teams workflows and NATS.io, a build system parameterized for company forks, CI skipped for docs-only changes, a move to pnpm. The selector revert says the project would rather live with awkward HPA math than break autoscaling for existing users, so progressive-delivery mechanics stay where they are.
1.10.0 looks likely to land close to rc1 — dependency, CVE and notification work with no controller-semantics change — and the HPA selector question stays open unless it returns behind an opt-in flag.
Gloo Gateway keeps maintaining 1.19, 1.20 and 1.21 in parallel. The 1.20.29 release fixes a failure where, after a gloo restart, a failed first reconcile sent every connected Envoy an empty config; it also keeps the in-memory Proxy store across setup re-runs and delays setup restarts until the first xDS sync. The 21 October batch had fixed proxies stuck on stale endpoints.
Recent work concentrates on control-plane failure modes: what Envoy receives when gloo restarts, reconciles badly or sends mismatched endpoint data. Each fix is backported across the supported lines alongside routine Go and dependency bumps.
The 1.21 and 1.19 backports of the empty-snapshot fix are the likely next entries, following the same-day batch pattern.
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 Argo Rollouts or Gloo Gateway.
Apptainer 1.6 candidate adds delta images that rebuild only what changed.
Coder ships the same security backports to three release lines in one afternoon.
Robusta's 0.54.0 alpha returns to features: Prometheus tenants by namespace and Holmes fixes.
ShenYu is cutting 2.7.2 release candidates, but the tags still carry no notes.
k0s ships another four-branch patch round, with an IPv6 service CIDR fix on 1.37 and 1.36.
Honeycomb's Canvas now remembers your systems and lays out each investigation in sections.
See all Argo Rollouts 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 Argo Rollouts alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Argo Rollouts alternatives" section above for the current picks, or visit /alternatives/argo-rollouts 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.