Lima
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
A side-by-side editorial comparison of Algolia and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.
Algolia's Agent Studio opens to outside agents and starts grading its own before they ship
October put Agent Studio in front. The A2A protocol lets external agents and orchestration frameworks discover and call Studio agents through standardized agent cards, and automated evaluations score an agent on relevance, faithfulness and tone before deployment, using test cases generated from the customer's search index. AI Assist gained a No results agent that diagnoses zero-result searches, and automated suggestions now recommend Dynamic Re-Ranking, Personalization and NeuralSearch from performance data. On the commerce side, retail media network orchestration reached general availability for Elevate Ecommerce customers.
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 →
October put Agent Studio in front. The A2A protocol lets external agents and orchestration frameworks discover and call Studio agents through standardized agent cards, and automated evaluations score an agent on relevance, faithfulness and tone before deployment, using test cases generated from the customer's search index. AI Assist gained a No results agent that diagnoses zero-result searches, and automated suggestions now recommend Dynamic Re-Ranking, Personalization and NeuralSearch from performance data. On the commerce side, retail media network orchestration reached general availability for Elevate Ecommerce customers.
Two tracks are running together. Agent Studio is collecting what a production agent platform needs, an interoperability standard and a pre-deployment test loop, while AI Assist and automated suggestions turn the dashboard into something that tells merchandisers what to change. Retail media GA and the combined-signal setting in Dynamic Re-Ranking show the commerce core still shipping beside the agent work rather than giving way to it.
Automated suggestions is described as an initial release covering three features, so more features joining it is the safest call. Evaluations also let teams compare runs, which points toward using scores to gate a configuration change, though the entries do not say that is planned.
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 Algolia or HAProxy Kubernetes Ingress Controller.
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
Snort 3.12.4 pairs a long memory-safety pass with detection speed work
Honeycomb is working on the first ten minutes, not just the incident
Talos 1.15's alpha keeps moving: a silent containerd config trap and declarative CPU control
Pinot 1.6 adds SQL DDL and vector backends, and now needs Java 25 to run its services.
See all Algolia 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. Algolia 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. Algolia 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 Algolia alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Algolia alternatives" section above for the current picks, or visit /alternatives/algolia 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.