ZoneMinder
ZoneMinder 1.38.5 fixes 19 vulnerabilities, including authenticated remote code execution
A side-by-side editorial comparison of Fluentd and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.
Fluentd 1.20 drops its yajl dependency to keep building on Ruby 4.1
Fluentd shipped 1.20.0 and 1.20.1 on the same day in late October. 1.20.0 replaces yajl with Ruby's built-in JSON, adds opt-in threaded parsing and directory watching to in_tail, a command timeout for in_exec, TCP keepalive for out_forward, a umask option and a cap on evacuated buffer chunks. 1.20.1 removed yajl-ruby from runtime dependencies because it cannot build on Ruby 4.1, so plugins that require it must now declare it themselves. 1.19.4 in September fixed buffer accounting leaks, a path traversal check and syslog limits.
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 →
Fluentd shipped 1.20.0 and 1.20.1 on the same day in late October. 1.20.0 replaces yajl with Ruby's built-in JSON, adds opt-in threaded parsing and directory watching to in_tail, a command timeout for in_exec, TCP keepalive for out_forward, a umask option and a cap on evacuated buffer chunks. 1.20.1 removed yajl-ruby from runtime dependencies because it cannot build on Ruby 4.1, so plugins that require it must now declare it themselves. 1.19.4 in September fixed buffer accounting leaks, a path traversal check and syslog limits.
The project is clearing old native dependencies ahead of new Ruby versions while making in_tail cheaper at high file counts. The hardening theme from 1.19.3 and 1.19.4 continues in the buffer and input paths.
Expect 1.20.x patches driven by plugins that break without yajl-ruby, since 1.20.1 pushes that dependency onto plugin authors.
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 Fluentd or HAProxy Kubernetes Ingress Controller.
ZoneMinder 1.38.5 fixes 19 vulnerabilities, including authenticated remote code execution
CRI-O ships patch releases across three branches with empty change notes
Certbot keeps tidying correctness bugs around renewals and hooks
Routinator 0.16 will validate ASPA and BGPsec, and run strict, by default
Buildkite drops long-lived GitHub credentials from self-hosted agents
AIReiter adds ByteDance's Seedream 5.0 Flash for fast, low-cost image generation and editing
See all Fluentd 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. Fluentd 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. Fluentd 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 Fluentd alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fluentd alternatives" section above for the current picks, or visit /alternatives/fluentd 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.