CRI-O
CRI-O ships patch releases across three branches with empty change notes
A side-by-side editorial comparison of HAProxy Kubernetes Ingress Controller and ZoneMinder — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | HAProxy Kubernetes Ingress Controller | ZoneMinder |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | ingress-controller, haproxy, kubernetes, patch-release | video-surveillance, security-hardening, rbac, api-authorization |
| Last editorial update | 10h ago | 1h ago |
| Website | Visit → | Visit → |
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 →
ZoneMinder 1.38.5 fixes 19 vulnerabilities, including authenticated remote code execution
ZoneMinder's 1.38 line is in security maintenance. 1.38.5 fixes 19 reported vulnerabilities, including authenticated OS command execution through the filter debug modal, a JPEG heap overflow and cross-monitor authorization bypasses. It replaces a default or empty auth hash secret on upgrade and refuses token logins while the public default is set. 1.38.6 followed within the hour only to fix RPM builds, since no 1.38.5 RPMs were published.
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.
ZoneMinder's 1.38 line is in security maintenance. 1.38.5 fixes 19 reported vulnerabilities, including authenticated OS command execution through the filter debug modal, a JPEG heap overflow and cross-monitor authorization bypasses. It replaces a default or empty auth hash secret on upgrade and refuses token logins while the public default is set. 1.38.6 followed within the hour only to fix RPM builds, since no 1.38.5 RPMs were published.
Every 1.38 release since June has been mostly authorization and memory-safety work. The 1.38.0 feature set (RBAC, WebRTC, the monitor function split) is being made safe rather than extended.
Further security releases on 1.38 are likely; the entries give no sign of a 1.39 feature release.
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 HAProxy Kubernetes Ingress Controller or ZoneMinder.
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
Dashy shipped ten releases in five days; one fixes how auth headers trust origins
See all HAProxy Kubernetes Ingress Controller alternatives → · See all ZoneMinder alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HAProxy Kubernetes Ingress Controller and ZoneMinder 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. HAProxy Kubernetes Ingress Controller and ZoneMinder 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 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.
Top ZoneMinder alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ZoneMinder alternatives" section above for the current picks, or visit /alternatives/zoneminder for the full list with editorial commentary on each.