Dashy
Dashy shipped ten releases in five days; one fixes how auth headers trust origins
A side-by-side editorial comparison of ClouDNS and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.
ClouDNS widens its SSL catalog and adds maintenance windows to monitoring
ClouDNS keeps adding direct registry accreditations, with .LOVE, .BAR, .CLICK, .TO, .DIY, .FOOD and others since mid-September. Alongside them it is building out the services around domains: Maintenance Mode for monitoring checks, new Status Page alert options, and now RapidSSL and Actalis certificates, including wildcard options.
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 →
ClouDNS keeps adding direct registry accreditations, with .LOVE, .BAR, .CLICK, .TO, .DIY, .FOOD and others since mid-September. Alongside them it is building out the services around domains: Maintenance Mode for monitoring checks, new Status Page alert options, and now RapidSSL and Actalis certificates, including wildcard options.
The registrar expansion continues at roughly one batch of TLDs a month, while monitoring and SSL become fuller products in their own right. The direction is a one-stop domain, DNS, certificate and uptime provider.
Another batch of TLD accreditations is the likeliest next entry; further monitoring features look likely given two releases since September.
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 ClouDNS 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
fossa-cli's feed jumps from 3.17 to 3.20, with clearer container scan errors.
Gloo Gateway's October batch fixes proxies that silently kept stale endpoints.
See all ClouDNS alternatives → · See all HAProxy Kubernetes Ingress Controller alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ClouDNS 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. ClouDNS 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 ClouDNS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ClouDNS alternatives" section above for the current picks, or visit /alternatives/cloudns 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.