← Back to home
Comparison · Infra & APIs

HAProxy Kubernetes Ingress Controller vs Jaeger

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

HAProxy Kubernetes Ingress Controller vs Jaeger: at a glance

FeatureHAProxy Kubernetes Ingress ControllerJaeger
SectorInfra & APIsInfra & APIs
Velocity score5.02.5
Sparks · 30d00
Top themesingress-controller, haproxy, kubernetes, patch-releasespan-search, mcp, clickhouse, elasticsearch
Last editorial update1h ago7h ago
WebsiteVisit →Visit →

What is HAProxy Kubernetes Ingress Controller?

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 →

What is Jaeger?

Jaeger's query service learns to search individual spans, not just whole traces.

Jaeger 2.21 and 2.22 extend the 2.x storage and query rework. ClickHouse storage moved to a stable feature gate in 2.21, and the release removed v1 HTTP endpoints the UI no longer calls. In 2.22 the query service gains FindSpans with RFC 0014 pagination, Elasticsearch span search, and structured filters promoted to beta, while native Elasticsearch trace summaries go stable.

Read the full Jaeger trajectory →

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

H5.0

Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

Expect further patches dominated by go.mod and Kubernetes client updates, with new capability waiting for a later line.

J
Jaeger
INFRA · APIS
2.5

Jaeger's query service learns to search individual spans, not just whole traces.

◆ Current state

Jaeger 2.21 and 2.22 extend the 2.x storage and query rework. ClickHouse storage moved to a stable feature gate in 2.21, and the release removed v1 HTTP endpoints the UI no longer calls. In 2.22 the query service gains FindSpans with RFC 0014 pagination, Elasticsearch span search, and structured filters promoted to beta, while native Elasticsearch trace summaries go stable.

◆ Where it's heading

The earlier trace-summaries work made search cheaper; span search changes what can be asked. Pagination and structured filters give both the UI and MCP clients a way to query without pulling whole traces. MCP keeps getting practical limits and input checks, and search_traces no longer needs a service name on backends that declare support for that.

◆ Prediction

Expect span search to spread beyond Elasticsearch and memory storage, and structured filters to move from beta to stable as other gates have. Further removal of v1 surface is likely, since 2.21 already started it.

Alternatives to HAProxy Kubernetes Ingress Controller and Jaeger

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 Jaeger.

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

Recent activity from HAProxy Kubernetes Ingress Controller and Jaeger

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

  1. 2d agoHAProxy Kubernetes Ingress Controllerv3.2.19: reload flag data race fix and x/ package bumps
  2. 12d agoHAProxy Kubernetes Ingress Controllerv3.2.18: keeps all TLS secrets per host, CRD panic fix
  3. 17d agoHAProxy Kubernetes Ingress Controllerv3.2.17: k8s.io, x/ and client-native dependency updates
  4. 25d agoHAProxy Kubernetes Ingress Controllerv3.2.16: dependency, CI and test maintenance
  5. 26d agoJaegerSpan search and pagination reach the query service
  6. 1mo agoJaegerClickHouse goes stable; unused v1 HTTP endpoints removed
  7. 1mo agoHAProxy Kubernetes Ingress Controllerv3.2.15: IngressClass ingestion fix, status rework, Go 1.27
  8. 2mo agoHAProxy Kubernetes Ingress Controllerssl-passthrough allow/deny lists retained on the https frontend
  9. 3mo agoJaegerMCP merges into the query service; Elasticsearch 6 support removed ⚡
  10. 5mo agoJaegerLightweight trace-summaries endpoint arrives in the v3 API
  11. 5mo agoJaegerHeader forwarding to storage backends and UI base-path autodetection
  12. 7mo agoJaegerClock-skew and jitter fixes; metrics storage exposed to the UI

Frequently asked questions

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

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 2.5), 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 HAProxy Kubernetes Ingress Controller better than Jaeger?

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 2.5), 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 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.

What are the best alternatives to Jaeger?

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