Inspektor Gadget
Inspektor Gadget keeps cutting the privileges an eBPF tool has to ask for.
A side-by-side editorial comparison of Dokku and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.
Dokku's autumn patches swap new features for safer deploys and stricter validation.
The 0.38 line reached v0.38.34 in late October, and the recent releases are mostly about correctness. Deploy locks now release on exit and honor apps:lock, app names and arguments are validated across commands, config write failures are reported, and dokku run propagates exit codes. Smaller additions include a --no-cache flag for ps:rebuild, per-entry cron MAILTO and a configurable nginx proxy HTTP version.
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 →
The 0.38 line reached v0.38.34 in late October, and the recent releases are mostly about correctness. Deploy locks now release on exit and honor apps:lock, app names and arguments are validated across commands, config write failures are reported, and dokku run propagates exit codes. Smaller additions include a --no-cache flag for ps:rebuild, per-entry cron MAILTO and a configurable nginx proxy HTTP version.
The August k3s parity push has given way to a hardening pass through commands that used to fail quietly. A second thread makes configuration declarative: storage mounts, scheduler-k3s metadata and chart overrides each gained a whole-set form, which suits automation tools more than people at a terminal. Machine use of the CLI remains the through-line.
Expect the whole-set form to reach more properties, since three subsystems have now gained it. Patch releases should stay frequent, and the notes give no sign of a move past the 0.38 line.
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 Dokku or HAProxy Kubernetes Ingress Controller.
Inspektor Gadget keeps cutting the privileges an eBPF tool has to ask for.
k0s opens its 1.37 line while security fixes ride the older branches.
Grype widens distro accuracy while each release clears its own dependency advisories.
Borg 2.0 beta 25 breaks repositories to swap its hash and repository format.
CrowdSec's 1.8.2 candidates let operators write their own bot fingerprints.
AdGuard Home renames its next release: the 0.108 beta line becomes v1.0.0.
See all Dokku 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. Dokku 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. Dokku 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 Dokku alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dokku alternatives" section above for the current picks, or visit /alternatives/dokku 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.