Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
Comparison · Infra & APIs
HAProxy Kubernetes Ingress Controller vs KubeArmor
A side-by-side editorial comparison of HAProxy Kubernetes Ingress Controller and KubeArmor — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:kubernetes
HAProxy Kubernetes Ingress Controller vs KubeArmor: 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 KubeArmor?
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
KubeArmor's feed shows five release-candidate tags and one merge-commit entry from October for 1.7.6 and 1.7.7, each carrying one or two commits: a relay-channel memory leak fix with pprof added, a snitch fix, removed limits and an AppArmor alert-throttling fix. GitHub shows 1.7.6 went final on 23 October, which the feed missed; it replaced the execve kprobe with a tracepoint, fixed pods not terminating on AppArmor nodes, added audit alerts from the BPF-LSM enforcer and expanded arm64 eBPF testing.
HAProxy Kubernetes Ingress Controller vs KubeArmor: 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.
KubeArmor
5.0INFRA · APIS
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
◆ Current state
KubeArmor's feed shows five release-candidate tags and one merge-commit entry from October for 1.7.6 and 1.7.7, each carrying one or two commits: a relay-channel memory leak fix with pprof added, a snitch fix, removed limits and an AppArmor alert-throttling fix. GitHub shows 1.7.6 went final on 23 October, which the feed missed; it replaced the execve kprobe with a tracepoint, fixed pods not terminating on AppArmor nodes, added audit alerts from the BPF-LSM enforcer and expanded arm64 eBPF testing.
◆ Where it's heading
The project is mid-way through stabilising its eBPF enforcement across architectures: arm64 syscall matching, multi-arch image tests and the move from kprobes to tracepoints all reduce kernel-specific breakage. The release process remains RC-heavy, with near-identical tags cut minutes apart, which makes the feed a poor guide to what users actually get.
◆ Prediction
Expect 1.7.7 final soon after rc1, carrying the AppArmor throttling fix. The arm64 work in 1.7.6 suggests further multi-architecture fixes rather than new policy features next.
Alternatives to HAProxy Kubernetes Ingress Controller and KubeArmor
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 KubeArmor.
Apache ShenYu
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
All Quiet
All Quiet moves from enterprise integrations to the on-call engineer's own day.
Robusta
Robusta's recent releases patch its runner image rather than add features.
Uptrends
Uptrends spent October on account plumbing: vault credentials, bulk edits and a free trial path.
See all HAProxy Kubernetes Ingress Controller alternatives → · See all KubeArmor alternatives →
Recent activity from HAProxy Kubernetes Ingress Controller and KubeArmor
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoHAProxy Kubernetes Ingress Controllerv3.2.19: reload flag data race fix and x/ package bumps
- 3d agoKubeArmor1.7.7-rc1 fixes AppArmor alert throttling
- 5d agoKubeArmorDuplicate 1.7.7-rc1 entry: AppArmor alert throttling fix
- 11d agoKubeArmor1.7.6-rc6 backports a snitch fix
- 12d agoHAProxy Kubernetes Ingress Controllerv3.2.18: keeps all TLS secrets per host, CRD panic fix
- 17d 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
- 27d agoKubeArmor1.7.6-rc5: a single 'remove limits' change
- 27d agoKubeArmor1.7.6-rc4 fixes a relay-channel memory leak, adds pprof
- 28d agoKubeArmor1.7.6-rc3: same commits as rc4
- 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
Frequently asked questions
What is the difference between HAProxy Kubernetes Ingress Controller and KubeArmor?
Both compete on the same themes — kubernetes — within Infra & APIs. HAProxy Kubernetes Ingress Controller and KubeArmor 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 KubeArmor?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HAProxy Kubernetes Ingress Controller and KubeArmor 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 KubeArmor?
Top KubeArmor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "KubeArmor alternatives" section above for the current picks, or visit /alternatives/kubearmor for the full list with editorial commentary on each.