GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of HAProxy Kubernetes Ingress Controller and Velociraptor — 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 →
Velociraptor's recent releases are mostly about patching CVEs.
Velociraptor 0.77.3 shipped on October 5 as a bug fix and CVE release; it also adds an artifact that uploads server results to Azure Monitor and trims the columns emitted by the backup artifacts. 0.77.2 and a 0.76.7 backport in September and August were CVE fixes. The 0.77.1 feature release landed in June, but its notes in the feed only link out.
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.
Velociraptor 0.77.3 shipped on October 5 as a bug fix and CVE release; it also adds an artifact that uploads server results to Azure Monitor and trims the columns emitted by the backup artifacts. 0.77.2 and a 0.76.7 backport in September and August were CVE fixes. The 0.77.1 feature release landed in June, but its notes in the feed only link out.
Since June the project has been in security mode, fixing CVEs on the current line and backporting to the previous one. Feature work shows up as new artifacts, here an Azure Monitor export, which keeps Velociraptor feeding results into the logging tools teams already use.
Expect further 0.77 patch releases and possibly another backport if new CVEs are published; the timing of a 0.78 feature release is not signaled here.
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 Velociraptor.
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 Velociraptor 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 is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HAProxy Kubernetes Ingress Controller is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.
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 Velociraptor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Velociraptor alternatives" section above for the current picks, or visit /alternatives/velociraptor for the full list with editorial commentary on each.