← Back to home
Comparison · Infra & APIs

HAProxy Kubernetes Ingress Controller vs Oh Dear

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

HAProxy Kubernetes Ingress Controller vs Oh Dear: at a glance

FeatureHAProxy Kubernetes Ingress ControllerOh Dear
SectorInfra & APIsInfra & APIs
Velocity score5.05.0
Sparks · 30d00
Top themesingress-controller, haproxy, kubernetes, patch-releaseuptime-monitoring, security, mcp, status-pages
Last editorial update2h ago54m 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 Oh Dear?

Oh Dear's weekly changelogs have carried a security section five weeks running.

Oh Dear, an uptime and site monitoring service, publishes a changelog each week. Since late September, along with features such as custom webhook headers, 30 to 90 days of status page history and AI fix prompts in Broken Links alerts, it has fixed a high-severity SSRF in uptime checks and AI page fetches, a status page CNAME takeover, a reflected XSS and a status page ID leak, restricted scoped API tokens from team-wide endpoints, and made the MCP consent screen show redirect destinations. The MCP URL now opens a landing page in a browser.

Read the full Oh Dear trajectory →

HAProxy Kubernetes Ingress Controller vs Oh Dear: 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.

O
Oh Dear
INFRA · APIS
5.0

Oh Dear's weekly changelogs have carried a security section five weeks running.

◆ Current state

Oh Dear, an uptime and site monitoring service, publishes a changelog each week. Since late September, along with features such as custom webhook headers, 30 to 90 days of status page history and AI fix prompts in Broken Links alerts, it has fixed a high-severity SSRF in uptime checks and AI page fetches, a status page CNAME takeover, a reflected XSS and a status page ID leak, restricted scoped API tokens from team-wide endpoints, and made the MCP consent screen show redirect destinations. The MCP URL now opens a landing page in a browser.

◆ Where it's heading

August's large MCP release opened the whole product to AI agents, and the autumn work is closing the gaps that kind of exposure creates: SSRF through AI page fetches, consent redirects and token scope. Several fixes credit outside reporters, which suggests responsible disclosure is active. Product work continues alongside in small, practical items for webhooks, status pages and resellers.

◆ Prediction

Expect security fixes to keep appearing in most weekly changelogs while outside reports continue. AI features are spreading into notifications, as the Broken Links fix prompts show, so more AI-written guidance inside alerts is likely.

Alternatives to HAProxy Kubernetes Ingress Controller and Oh Dear

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 Oh Dear.

See all HAProxy Kubernetes Ingress Controller alternatives → · See all Oh Dear alternatives →

Recent activity from HAProxy Kubernetes Ingress Controller and Oh Dear

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

  1. 2d agoOh DearWebhook custom headers, uptime header rules, reseller teams page
  2. 2d agoHAProxy Kubernetes Ingress Controllerv3.2.19: reload flag data race fix and x/ package bumps
  3. 9d agoOh DearAI fix prompts in Broken Links alerts, PHP CVE warnings
  4. 9d agoOh DearScoped tokens locked out of team-wide endpoints
  5. 12d agoHAProxy Kubernetes Ingress Controllerv3.2.18: keeps all TLS secrets per host, CRD panic fix
  6. 15d agoOh DearHigh-severity SSRF fixed in uptime checks and AI fetches
  7. 17d agoHAProxy Kubernetes Ingress Controllerv3.2.17: k8s.io, x/ and client-native dependency updates
  8. 26d agoHAProxy Kubernetes Ingress Controllerv3.2.16: dependency, CI and test maintenance
  9. 1mo agoOh DearLonger status page history; MCP consent and CNAME fixes
  10. 1mo agoOh DearWebhook deep links; one slow monitor no longer stalls others
  11. 1mo agoHAProxy Kubernetes Ingress Controllerv3.2.15: IngressClass ingestion fix, status rework, Go 1.27
  12. 2mo agoHAProxy Kubernetes Ingress Controllerssl-passthrough allow/deny lists retained on the https frontend

Frequently asked questions

What is the difference between HAProxy Kubernetes Ingress Controller and Oh Dear?

They serve adjacent needs but don't currently overlap on shipped themes. HAProxy Kubernetes Ingress Controller and Oh Dear 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.

Is HAProxy Kubernetes Ingress Controller better than Oh Dear?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HAProxy Kubernetes Ingress Controller and Oh Dear 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.

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 Oh Dear?

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