Jackett
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
A side-by-side editorial comparison of Lima and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Lima | HAProxy Kubernetes Ingress Controller |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 2.5 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | local virtualization, guest os support, windows guests, agent sandboxing | kubernetes-ingress, haproxy, commit-log-changelog, security-hardening |
| Last editorial update | 4h ago | 3h ago |
| Website | Visit → | Visit → |
Lima keeps adding guest operating systems, and a flag to stop AI agents wrecking the host.
Lima's release stream is a steady widening of what it can boot. The 2.1 line added experimental macOS and FreeBSD guests and a limactl shell --sync flag intended to keep AI agents from breaking host files; the 2.2 betas add experimental Windows Server 2025 and Windows 11 guests, TPM emulation under QEMU, a limactl screenshot command, and an option to turn off password-less sudo. Between those, the tags are CLI fixes and template maintenance.
The changelog is a raw commit log, and its severity tags tell you more than the prose would.
Every release note is a list of commit hashes with HAProxy's own severity prefixes attached — BUILD/MINOR, BUG/MEDIUM, TEST/MINOR, MAJOR. Two of the six releases in this window contain nothing but go.mod and base image bumps. The 3.2.x line ships roughly every two to four weeks and stays entirely within patch scope.
Read the full HAProxy Kubernetes Ingress Controller trajectory →
Lima's release stream is a steady widening of what it can boot. The 2.1 line added experimental macOS and FreeBSD guests and a limactl shell --sync flag intended to keep AI agents from breaking host files; the 2.2 betas add experimental Windows Server 2025 and Windows 11 guests, TPM emulation under QEMU, a limactl screenshot command, and an option to turn off password-less sudo. Between those, the tags are CLI fixes and template maintenance.
A tool that began as Linux VMs on macOS is becoming a general local virtualization front end, with macOS, FreeBSD, and Windows guests all arriving inside two release lines and much of it contributed through mentorship programs. A second thread is tightening the host boundary, with the sync flag, the sudo opt-out, and TPM emulation all narrowing what a guest can assume or reach. Everything guest-related is still marked experimental.
Each guest platform has arrived experimental and then accumulated follow-up pull requests; Windows support is at that stage now, so the next releases most likely stabilize it rather than add another operating system.
Every release note is a list of commit hashes with HAProxy's own severity prefixes attached — BUILD/MINOR, BUG/MEDIUM, TEST/MINOR, MAJOR. Two of the six releases in this window contain nothing but go.mod and base image bumps. The 3.2.x line ships roughly every two to four weeks and stays entirely within patch scope.
The interesting arc is traceable through the tags. v3.2.7 landed two commits marked MAJOR — feature and security improvements to the haproxy wrapper and to block secrets protection — and five releases later v3.2.12 fixes a BUG/MEDIUM described as a block_secrets stability regression. The security hardening introduced instability that took nearly two months to surface and correct. Alongside that, the recurring subject is Kubernetes resource resolution: ExternalName backends bypassed by orphan EndpointSlices, ssl-passthrough mode resolved too late to build rules correctly.
Expect the 3.2.x line to continue absorbing fallout from the 3.2.7 hardening work and further edge cases in service resolution; the deprecation of the cookie-persistence annotation in 3.2.11 suggests annotation cleanup is also in progress.
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 Lima or HAProxy Kubernetes Ingress Controller.
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
Ten days of bulk operations, then the AI assistant got the keys to multi-site access control.
A v5 release candidate train carrying a database migrator that has to work on the first try.
The syslog daemon is quietly becoming an OpenTelemetry-era pipeline, YAML config and all.
Three supported branches, patched in lockstep within the same minute.
The eBPF observability tool just started reaching for the GPU.
See all Lima 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. Lima is currently shipping more aggressively (velocity 2.5 vs 0.0), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Lima is currently shipping more aggressively (velocity 2.5 vs 0.0), 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.
Top Lima alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Lima alternatives" section above for the current picks, or visit /alternatives/lima 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.