NetBox
NetBox 4.7's patch run fixes a token leak and a broken restore path.
A side-by-side editorial comparison of Coder and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.
Coder now patches three release lines at once, and the fixes keep landing on agent access.
Coder's feed shows patch releases on v2.29, v2.34 and v2.36 within three days, which means a v2.35 and a v2.36 mainline shipped that this feed never captured. The late-October fixes are permission work: new API keys stay within the caller's scopes, fetching external agent credentials now requires SSH permission, and read_skill_file reads are confined to the skill directory. Everything else is release-script and DERP client fixes.
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 →
Coder's feed shows patch releases on v2.29, v2.34 and v2.36 within three days, which means a v2.35 and a v2.36 mainline shipped that this feed never captured. The late-October fixes are permission work: new API keys stay within the caller's scopes, fetching external agent credentials now requires SSH permission, and read_skill_file reads are confined to the skill directory. Everything else is release-script and DERP client fixes.
The security surface is moving to the AI agent features. Two of the three substantive fixes this round concern what an agent can read or which credentials it can obtain, following the June hardening drop on OIDC linking and token theft. The multi-branch backporting continues, so enterprise customers on older lines like 2.29 still get the same permission fixes as the mainline.
Expect more permission checks around agent credentials and skills as those features get exercised; the feature releases themselves are not visible in this feed, so their direction is unclear from these entries.
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 Coder or HAProxy Kubernetes Ingress Controller.
NetBox 4.7's patch run fixes a token leak and a broken restore path.
Apptainer's CDI support needed a privilege-escalation fix four months after it shipped.
Cobbler's 3.3 branch adds Kerberos single sign-on to the web UI.
Oh Dear's weekly changelogs have carried a security section five weeks running.
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
See all Coder 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. Coder 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. Coder 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 Coder alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Coder alternatives" section above for the current picks, or visit /alternatives/coder 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.