← Back to home
Comparison · Infra & APIs

FoRecoML vs HAProxy Kubernetes Ingress Controller

A side-by-side editorial comparison of FoRecoML and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.

FoRecoML vs HAProxy Kubernetes Ingress Controller: at a glance

FeatureFoRecoMLHAProxy Kubernetes Ingress Controller
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themesforecasting, machine-learning, hierarchical-reconciliation, time-serieskubernetes, ingress, ssl-passthrough, correctness
Last editorial update56m ago3d ago
WebsiteVisit →Visit →

What is FoRecoML?

The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.

FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.

Read the full FoRecoML trajectory →

What is HAProxy Kubernetes Ingress Controller?

Nine months into the 3.2 line, HAProxy Ingress is still repairing ssl-passthrough and ingress merge order.

The controller ships a steady patch cadence on the 3.2 branch, roughly one release every two to four weeks. Content is almost entirely correctness work: ssl-passthrough handling and the rules that decide which Ingress object owns a shared backend. Feature additions are absent from the last ten releases; dependency bumps to k8s.io and golang.org/x packages appear in most of them.

Read the full HAProxy Kubernetes Ingress Controller trajectory →

FoRecoML vs HAProxy Kubernetes Ingress Controller: editorial side-by-side

F
FoRecoML
INFRA · APIS
0.0

The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.

◆ Current state

FoRecoML brings machine-learning approaches to forecast reconciliation across cross-sectional, temporal, and cross-temporal frameworks through csrml(), terml(), and ctrml(). It reached CRAN in April 2026 and has since spent both releases integrating with FoReco rather than expanding its own method set: results are now FoReco's foreco objects, and print() and summary() report framework, approach, problem dimensions, features, training sample size, combination matrix, and trained models.

◆ Where it's heading

This package is being built as a satellite, not a competitor. Adopting FoReco's exported new_foreco_class() constructor within days of that class appearing means FoRecoML results drop straight into the same print, summary, plot, and components methods as analytically reconciled ones — which is what makes machine-learning and classical reconciliation directly comparable in a single workflow. The 1.1.1 argument-validation work landed in the same minute as the equivalent change in FoReco, so the two are being maintained as one release train.

◆ Prediction

With the integration work done, the next release is more likely to add or expose machine-learning approaches than to keep reshaping output; the structured summary already enumerates features and trained models, which suggests inspection tooling is where attention has been.

H2.5

Nine months into the 3.2 line, HAProxy Ingress is still repairing ssl-passthrough and ingress merge order.

◆ Current state

The controller ships a steady patch cadence on the 3.2 branch, roughly one release every two to four weeks. Content is almost entirely correctness work: ssl-passthrough handling and the rules that decide which Ingress object owns a shared backend. Feature additions are absent from the last ten releases; dependency bumps to k8s.io and golang.org/x packages appear in most of them.

◆ Where it's heading

v3.2.13 is the largest release in the window and marks a shift from patching individual ssl-passthrough bugs to defining the semantics properly: backends are now reconciled rather than recreated, the invariant is applied before anything that can fail, and controller-owned backend state survives a failed transaction. Alongside it, ingress merge order became deterministic — oldest ingress first — and the first Ingress to constitute a backend now owns it, with the annotations a losing Ingress forfeits named explicitly. That pairing suggests the team traced a class of flapping and non-reproducible config bugs back to undefined ordering.

◆ Prediction

Expect the next few releases to stay on the 3.2 patch line, adding tests around the new ownership and passthrough invariants rather than new annotations.

Alternatives to FoRecoML and HAProxy Kubernetes Ingress Controller

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 FoRecoML or HAProxy Kubernetes Ingress Controller.

See all FoRecoML alternatives → · See all HAProxy Kubernetes Ingress Controller alternatives →

Recent activity from FoRecoML and HAProxy Kubernetes Ingress Controller

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4d agoHAProxy Kubernetes Ingress ControllerDeterministic ingress merge order and reconciled ssl-passthrough backends
  2. 1mo agoFoRecoMLStructured print and summary for fitted reconciliation models
  3. 1mo agoHAProxy Kubernetes Ingress Controllerssl-passthrough mode now resolved before rules are built
  4. 1mo agoFoRecoMLAdopts FoReco's foreco class for all reconciliation output
  5. 2mo agoHAProxy Kubernetes Ingress ControllerStops continuous reloads on default log config; deprecates cookie-persistence
  6. 2mo agoHAProxy Kubernetes Ingress ControllerExternalName backends no longer bypassed by orphan EndpointSlices
  7. 2mo agoHAProxy Kubernetes Ingress ControllerDependency bumps only
  8. 3mo agoHAProxy Kubernetes Ingress ControllerDependency bumps and Go 1.26 base image
  9. 3mo agoFoRecoMLMachine-learning forecast reconciliation arrives on CRAN

Frequently asked questions

What is the difference between FoRecoML and HAProxy Kubernetes Ingress Controller?

They serve adjacent needs but don't currently overlap on shipped themes. HAProxy Kubernetes Ingress Controller is currently shipping more aggressively (velocity 2.5 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.

Is FoRecoML better than HAProxy Kubernetes Ingress Controller?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HAProxy Kubernetes Ingress Controller is currently shipping more aggressively (velocity 2.5 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.

What are the best alternatives to FoRecoML?

Top FoRecoML alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "FoRecoML alternatives" section above for the current picks, or visit /alternatives/forecoml for the full list with editorial commentary on each.

What are the best alternatives to HAProxy Kubernetes Ingress Controller?

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.