Dashy
Dashy shipped ten releases in five days; one fixes how auth headers trust origins
A side-by-side editorial comparison of Gloo Gateway and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.
Gloo Gateway's October batch fixes proxies that silently kept stale endpoints.
Gloo Gateway still maintains 1.19, 1.20 and 1.21 in parallel and releases them in same-day batches. The 2026-10-21 batch fixes a bug where a placeholder EDS assignment carried the wrong cluster name, so a proxy received an update it could not match, kept its old endpoints and never recovered. Each line also moved to Go 1.26.10; 1.21 additionally upgraded kin-openapi.
Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies
The controller remains on the 3.2 patch line. Since v3.2.14 the only release of substance is v3.2.15, which stopped filtering ingresses on IngressClass name at ingestion, reworked status publishing and moved to Go 1.27. Later patches are mainly dependency and tooling updates, with v3.2.18 keeping every TLS secret of an ingress on the same host and v3.2.19 fixing a data race on the reload flag.
Read the full HAProxy Kubernetes Ingress Controller trajectory →
Gloo Gateway still maintains 1.19, 1.20 and 1.21 in parallel and releases them in same-day batches. The 2026-10-21 batch fixes a bug where a placeholder EDS assignment carried the wrong cluster name, so a proxy received an update it could not match, kept its old endpoints and never recovered. Each line also moved to Go 1.26.10; 1.21 additionally upgraded kin-openapi.
Releases remain maintenance: Go and Kubernetes bumps on a weekly rhythm, with an occasional real bug fix shipped to every line at once. The 1.18 line no longer appears in the October batches. No new features are visible.
Expect further same-day dependency batches across the three lines; the entries show no feature release coming.
The controller remains on the 3.2 patch line. Since v3.2.14 the only release of substance is v3.2.15, which stopped filtering ingresses on IngressClass name at ingestion, reworked status publishing and moved to Go 1.27. Later patches are mainly dependency and tooling updates, with v3.2.18 keeping every TLS secret of an ingress on the same host and v3.2.19 fixing a data race on the reload flag.
The ssl-passthrough theme has faded, and the series is now closer to routine upkeep than stabilization. Fixes have moved to ingress class handling, TLS secret storage and concurrency, with test coverage arriving in the same changes. Patches keep coming, but no new configuration surface has appeared on this line in the entries shown, apart from amending the SSL frontend through a custom resource in v3.2.15.
Expect further patches dominated by go.mod and Kubernetes client updates, with new capability waiting for a later line.
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 HAProxy Kubernetes Ingress Controller.
Dashy shipped ten releases in five days; one fixes how auth headers trust origins
Mergify's merge queue now hunts the breaking PR by rerunning failed tests first
Fluentd 1.20 drops its yajl dependency to keep building on Ruby 4.1
WorkOS spent October giving IT admins control of Pipes and audit trails
ClouDNS widens its SSL catalog and adds maintenance windows to monitoring
fossa-cli's feed jumps from 3.17 to 3.20, with clearer container scan errors.
See all Gloo Gateway alternatives → · See all HAProxy Kubernetes Ingress Controller alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — kubernetes — within Infra & APIs. Gloo Gateway and HAProxy Kubernetes Ingress Controller are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 and HAProxy Kubernetes Ingress Controller are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
Top HAProxy Kubernetes Ingress Controller alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "HAProxy Kubernetes Ingress Controller alternatives" section above for the current picks, or visit /alternatives/haproxy-ingress for the full list with editorial commentary on each.