Dashy
A release per merged PR, and right now nearly every one is a translation string.
Comparison · Infra & APIs
HAProxy Kubernetes Ingress Controller vs PocketBase
A side-by-side editorial comparison of HAProxy Kubernetes Ingress Controller and PocketBase — release velocity, themes, recent moves, and the top alternatives to consider.
HAProxy Kubernetes Ingress Controller vs PocketBase: at a glance
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 →
What is PocketBase?
PocketBase ships small, twice — every 0.39 release gets a matching 0.22 backport for users who never moved.
PocketBase releases every one to two weeks in tight pairs: a 0.39 patch and a 0.22 backport carrying whatever subset applies. The content is consistently small — admin UI fixes, dependency bumps, SQLite and goja updates — with occasional security work. The most consequential recent decision was replacing ozzo-validation with an in-house fork after the upstream library changed ownership.
HAProxy Kubernetes Ingress Controller vs PocketBase: editorial side-by-side
HAProxy Kubernetes Ingress Controller
2.5INFRA · APIS
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.
PocketBase
5.0INFRA · APIS
PocketBase ships small, twice — every 0.39 release gets a matching 0.22 backport for users who never moved.
◆ Current state
PocketBase releases every one to two weeks in tight pairs: a 0.39 patch and a 0.22 backport carrying whatever subset applies. The content is consistently small — admin UI fixes, dependency bumps, SQLite and goja updates — with occasional security work. The most consequential recent decision was replacing ozzo-validation with an in-house fork after the upstream library changed ownership.
◆ Where it's heading
This is a mature single-maintainer project in steady maintenance, prioritizing dependency hygiene and supply-chain caution over new capability. Two things are explicitly deferred to the future: proper non-zero exit code support for CLI commands, held back to v0.40 or v0.41 after a panic-recovery change was reverted, and eventually replacing ozzo-validation with a purpose-built validator. The continued 0.22 backports show a real installed base that hasn't migrated.
◆ Prediction
The deferred CLI exit-code work marks v0.40 as the next feature release rather than another patch. Expect the 0.39 and 0.22 pairing to continue until 0.22 is formally retired.
Alternatives to HAProxy Kubernetes Ingress Controller and PocketBase
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 PocketBase.
Talos Linux
Talos 1.14 reaches its release candidate with routing and DNS pulled into the OS
v0 by Vercel
v0 is turning a prompt-to-app toy into an addressable build service with a real workspace around it.
Cloudflare Tunnel
cloudflared's release feed is checksums and nothing else — until a release has to warn you off itself.
ToolJet
ToolJet's LTS line is where the features land now, while beta collects single-line fixes.
GravityKit
GravityKit ships a weekly Launch Log, and the interesting work is buried inside it
See all HAProxy Kubernetes Ingress Controller alternatives → · See all PocketBase alternatives →
Recent activity from HAProxy Kubernetes Ingress Controller and PocketBase
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoHAProxy Kubernetes Ingress ControllerDeterministic ingress merge order and reconciled ssl-passthrough backends
- 1d agoPocketBaseAPI preview fixes, UI polish, and Go dependency bumps
- 1d agoPocketBase0.22 LTS backport of the Go dependency bumps
- 16d agoPocketBaseCLI panic recovery reverted to restore non-zero exit codes
- 16d agoPocketBase0.22 LTS backport of the CLI exit-code revert
- 24d agoPocketBaseFirefox bulk-select fix, goja and filter-parser updates
- 24d agoPocketBase0.22 LTS backport of the goja and fexpr bumps
- 1mo agoHAProxy Kubernetes Ingress Controllerssl-passthrough mode now resolved before rules are built
- 1mo agoHAProxy Kubernetes Ingress ControllerStops continuous reloads on default log config; deprecates cookie-persistence
- 2mo agoHAProxy Kubernetes Ingress ControllerExternalName backends no longer bypassed by orphan EndpointSlices
- 2mo agoHAProxy Kubernetes Ingress ControllerDependency bumps only
- 2mo agoHAProxy Kubernetes Ingress ControllerDependency bumps and Go 1.26 base image
Frequently asked questions
What is the difference between HAProxy Kubernetes Ingress Controller and PocketBase?
They serve adjacent needs but don't currently overlap on shipped themes. PocketBase 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 PocketBase?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. PocketBase 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 PocketBase?
Top PocketBase alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PocketBase alternatives" section above for the current picks, or visit /alternatives/pocketbase for the full list with editorial commentary on each.