Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of All Quiet and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.
All Quiet moves from enterprise integrations to the on-call engineer's own day.
All Quiet is an incident management and on-call tool. Three releases on 28 September rebuilt the on-call calendar with effective and detailed views and overrides from any cell, added recurring snooze windows per integration plus detection of incidents that resolve themselves quickly, and introduced a personal on-call dashboard with shift summaries and noise metrics. Before that, August and early September added scoped API keys, Salesforce and Jira two-way sync and webhook rate-limit alerts.
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 →
All Quiet is an incident management and on-call tool. Three releases on 28 September rebuilt the on-call calendar with effective and detailed views and overrides from any cell, added recurring snooze windows per integration plus detection of incidents that resolve themselves quickly, and introduced a personal on-call dashboard with shift summaries and noise metrics. Before that, August and early September added scoped API keys, Salesforce and Jira two-way sync and webhook rate-limit alerts.
The summer work targeted buyers: access control and integrations that larger organisations require. The September work targets responders: less noise, clearer schedules and a view of one's own shifts. Noise detection for auto-resolving incidents is the most consequential piece, since it turns alert fatigue into a metric teams can act on.
Expect noise metrics to feed into suppression or routing rules, since detection without action is the obvious next gap. The feed has no entries after 28 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 All Quiet or HAProxy Kubernetes Ingress Controller.
Oh Dear's weekly changelogs have carried a security section five weeks running.
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
Robusta's recent releases patch its runner image rather than add features.
Uptrends spent October on account plumbing: vault credentials, bulk edits and a free trial path.
See all All Quiet 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. HAProxy Kubernetes Ingress Controller 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. HAProxy Kubernetes Ingress Controller 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 All Quiet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "All Quiet alternatives" section above for the current picks, or visit /alternatives/allquiet 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.