NetBox
NetBox 4.7's patch run fixes a token leak and a broken restore path.
A side-by-side editorial comparison of Cobbler and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.
Cobbler's 3.3 branch adds Kerberos single sign-on to the web UI.
Cobbler's public releases are all 3.3-branch backports. 3.3.10 adds Kerberos/GSSAPI single sign-on for the web UI through an Apache-terminated bridge and hardens the passthru authentication module against timing attacks. It follows the 3.3.8/3.3.9 pair, which brought openSUSE Leap 16 and Agama installer support, XCP-ng network installs and Python 3.13 support, and had to be re-cut after a CI publishing failure.
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 →
Cobbler's public releases are all 3.3-branch backports. 3.3.10 adds Kerberos/GSSAPI single sign-on for the web UI through an Apache-terminated bridge and hardens the passthru authentication module against timing attacks. It follows the 3.3.8/3.3.9 pair, which brought openSUSE Leap 16 and Agama installer support, XCP-ng network installs and Python 3.13 support, and had to be re-cut after a CI publishing failure.
The branch is still gaining features aimed at enterprise data centres rather than winding down: new installer ecosystems in August, directory-backed single sign-on now. Authentication has been a recurring concern since the CVE-2024-47533 admin-API bypass. Releases continue to arrive as rollups from main.
Expect further 3.3.x rollups; whether the main line cuts a 3.4 is not visible 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 Cobbler 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.
Coder now patches three release lines at once, and the fixes keep landing on agent access.
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 Cobbler 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. HAProxy Kubernetes Ingress Controller is currently shipping more aggressively (velocity 5.0 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. HAProxy Kubernetes Ingress Controller is currently shipping more aggressively (velocity 5.0 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 Cobbler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cobbler alternatives" section above for the current picks, or visit /alternatives/cobbler 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.