GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of HAProxy Kubernetes Ingress Controller and Hatchet — release velocity, themes, recent moves, and the top alternatives to consider.
HAProxy's ingress controller jumps to 3.4, drops Gateway API and config snippets.
After nineteen 3.2 patches, the controller released v3.4.0 on 12 November on top of HAProxy 3.4. It removes Gateway API support and config snippet annotations, announces further annotation deprecations, and retires the server-slot annotations by creating and deleting backend servers through HAProxy's runtime API. Custom resources that HAProxy rejects are now set aside and counted in a metric instead of breaking the config.
Read the full HAProxy Kubernetes Ingress Controller trajectory →
Hatchet chases DAG crash loops through three engine patches in a day.
Hatchet added sandboxes, Labs switches and cloud MFA in early November. The week since has been engine reliability: v0.120.3 batches DAG step triggers, v0.120.4 fixes stranded match rows and prunes database partitions before locking, and v0.120.5 removes another cause of DAG crash loops. Python SDK 1.46.0 makes it easier to unit-test tasks and passes failures to cleanup dependencies.
After nineteen 3.2 patches, the controller released v3.4.0 on 12 November on top of HAProxy 3.4. It removes Gateway API support and config snippet annotations, announces further annotation deprecations, and retires the server-slot annotations by creating and deleting backend servers through HAProxy's runtime API. Custom resources that HAProxy rejects are now set aside and counted in a metric instead of breaking the config.
The project is narrowing its configuration surface to its own custom resources: snippets and Gateway API are gone, annotations are being deprecated, and the 3.2 line had already added Frontend amendments through a custom resource. Runtime API server changes and the rejected-resource handling point to fewer reloads and fewer config-wide failures.
Expect 3.4 patch releases fixing migration problems for users who relied on snippets or deprecated annotations, and a published removal schedule for the annotations announced as deprecated.
Hatchet added sandboxes, Labs switches and cloud MFA in early November. The week since has been engine reliability: v0.120.3 batches DAG step triggers, v0.120.4 fixes stranded match rows and prunes database partitions before locking, and v0.120.5 removes another cause of DAG crash loops. Python SDK 1.46.0 makes it easier to unit-test tasks and passes failures to cleanup dependencies.
After a burst of features, Hatchet is tuning the engine under load: fewer locks, batched triggers and crash-loop fixes. The SDKs are getting testing and correctness work to match.
Expect more v0.120.x patches on DAG handling, then a sandbox package out of release candidate.
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 Hatchet.
GravityKit folds every GravityView extension into one Pro plugin.
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Clair 4.10 RC can read SBOMs to match Java vulnerabilities.
Shuffle tags builds almost daily, but the notes are empty.
KrakenD's community edition is shipping only dependency bumps.
See all HAProxy Kubernetes Ingress Controller alternatives → · See all Hatchet alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HAProxy Kubernetes Ingress Controller and Hatchet are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. HAProxy Kubernetes Ingress Controller and Hatchet are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
Top Hatchet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Hatchet alternatives" section above for the current picks, or visit /alternatives/hatchet for the full list with editorial commentary on each.