ZoneMinder
ZoneMinder 1.38.5 fixes 19 vulnerabilities, including authenticated remote code execution
Comparison · Infra & APIs
HAProxy Kubernetes Ingress Controller vs Routinator
A side-by-side editorial comparison of HAProxy Kubernetes Ingress Controller and Routinator — release velocity, themes, recent moves, and the top alternatives to consider.
HAProxy Kubernetes Ingress Controller vs Routinator: at a glance
What is HAProxy Kubernetes Ingress Controller?
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 →
What is Routinator?
Routinator 0.16 will validate ASPA and BGPsec, and run strict, by default
Routinator is a mature RPKI validator with a slow, release-candidate-gated cadence. After a run of security work, including an external audit's four CVEs in 0.15.2 and resource-exhaustion fixes in 0.15.3, 0.16.0-rc1 changes defaults: ASPA and BGPsec are on, strict validation is on, and the old enable flags become --disable-aspa, --disable-bgpsec and --relaxed. It also adds Resource Signed Checklists (RFC 9323), SLURM v2 with ASPA filtering, and a new repository logging scheme that changes the /status JSON.
HAProxy Kubernetes Ingress Controller vs Routinator: editorial side-by-side
HAProxy Kubernetes Ingress Controller
5.0INFRA · APIS
Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Expect further patches dominated by go.mod and Kubernetes client updates, with new capability waiting for a later line.
Routinator
5.0INFRA · APIS
Routinator 0.16 will validate ASPA and BGPsec, and run strict, by default
◆ Current state
Routinator is a mature RPKI validator with a slow, release-candidate-gated cadence. After a run of security work, including an external audit's four CVEs in 0.15.2 and resource-exhaustion fixes in 0.15.3, 0.16.0-rc1 changes defaults: ASPA and BGPsec are on, strict validation is on, and the old enable flags become --disable-aspa, --disable-bgpsec and --relaxed. It also adds Resource Signed Checklists (RFC 9323), SLURM v2 with ASPA filtering, and a new repository logging scheme that changes the /status JSON.
◆ Where it's heading
Having spent 2026 hardening the validator, the maintainers are now changing what operators get out of the box. Defaults moving toward ASPA and strictness put newer RPKI object types on equal footing with route origin validation.
◆ Prediction
A final 0.16.0 following one or more release candidates is the likely next step, as with 0.15.0.
Alternatives to HAProxy Kubernetes Ingress Controller and Routinator
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 Routinator.
CRI-O
CRI-O ships patch releases across three branches with empty change notes
Certbot
Certbot keeps tidying correctness bugs around renewals and hooks
Buildkite
Buildkite drops long-lived GitHub credentials from self-hosted agents
AIReiter
AIReiter adds ByteDance's Seedream 5.0 Flash for fast, low-cost image generation and editing
Dashy
Dashy shipped ten releases in five days; one fixes how auth headers trust origins
See all HAProxy Kubernetes Ingress Controller alternatives → · See all Routinator alternatives →
Recent activity from HAProxy Kubernetes Ingress Controller and Routinator
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoHAProxy Kubernetes Ingress Controllerv3.2.19: reload flag data race fix and x/ package bumps
- 4d agoRoutinatorRoutinator 0.16.0-rc1: ASPA, BGPsec and strict mode on by default
- 6d agoRoutinatorRoutinator 0.15.3 fixes resource-exhaustion paths
- 13d agoHAProxy Kubernetes Ingress Controllerv3.2.18: keeps all TLS secrets per host, CRD panic fix
- 18d agoHAProxy Kubernetes Ingress Controllerv3.2.17: k8s.io, x/ and client-native dependency updates
- 26d agoHAProxy Kubernetes Ingress Controllerv3.2.16: dependency, CI and test maintenance
- 1mo agoHAProxy Kubernetes Ingress Controllerv3.2.15: IngressClass ingestion fix, status rework, Go 1.27
- 2mo agoHAProxy Kubernetes Ingress Controllerssl-passthrough allow/deny lists retained on the https frontend
- 4mo agoRoutinatorSecurity audit closes four CVEs in 0.15.2
- 1y agoRoutinator0.15.1 stops empty-dataset starts and unblocks privileged ports
- 1y agoRoutinator0.15.0 reworks RRDP timeouts and separates repository-issue logs
- 1y agoRoutinator0.15.0-rc1 preview of the RRDP timeout rework
Frequently asked questions
What is the difference between HAProxy Kubernetes Ingress Controller and Routinator?
They serve adjacent needs but don't currently overlap on shipped themes. HAProxy Kubernetes Ingress Controller and Routinator 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.
Is HAProxy Kubernetes Ingress Controller better than Routinator?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HAProxy Kubernetes Ingress Controller and Routinator 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.
What are the best alternatives to HAProxy Kubernetes Ingress Controller?
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.
What are the best alternatives to Routinator?
Top Routinator alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Routinator alternatives" section above for the current picks, or visit /alternatives/routinator for the full list with editorial commentary on each.