Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
Comparison · Infra & APIs
HAProxy Kubernetes Ingress Controller vs k0s
A side-by-side editorial comparison of HAProxy Kubernetes Ingress Controller and k0s — release velocity, themes, recent moves, and the top alternatives to consider.
HAProxy Kubernetes Ingress Controller vs k0s: 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 k0s?
k0s opens its 1.37 line while security fixes ride the older branches.
k0s published v1.37.1 alongside 1.36.5, 1.35.9 and 1.34.12 on the same morning, so four branches are now live. The older branches took Kubernetes patch bumps, etcd 3.6.15 and deferred manifest directory creation, and 1.36 also scoped the worker autopilot to its own Node. In September, 1.36.4+k0s.1 and 1.35.8+k0s.1 shipped a fix for GHSA-qjgc-wmg7-3jc3, with csr-approver hardening on the 1.35 branch.
HAProxy Kubernetes Ingress Controller vs k0s: 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.
k0s
5.0INFRA · APIS
k0s opens its 1.37 line while security fixes ride the older branches.
◆ Current state
k0s published v1.37.1 alongside 1.36.5, 1.35.9 and 1.34.12 on the same morning, so four branches are now live. The older branches took Kubernetes patch bumps, etcd 3.6.15 and deferred manifest directory creation, and 1.36 also scoped the worker autopilot to its own Node. In September, 1.36.4+k0s.1 and 1.35.8+k0s.1 shipped a fix for GHSA-qjgc-wmg7-3jc3, with csr-approver hardening on the 1.35 branch.
◆ Where it's heading
The branch-parallel pattern is holding and now has a new top line. Lifecycle safety stays the core work: reset steps wired to contexts, autopilot retries and discovery refreshes, and autopilot scope limited to its own node. The 1.37 notes read as a long development log rather than a curated release, which fits a project that lets upstream Kubernetes carry the feature story.
◆ Prediction
Expect the next Kubernetes patch round to reach all four branches within hours of each other, and the oldest of them to drop off now that 1.37 is out, though these notes do not state a support window.
Alternatives to HAProxy Kubernetes Ingress Controller and k0s
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 k0s.
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.
KubeArmor
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
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.
See all HAProxy Kubernetes Ingress Controller alternatives → · See all k0s alternatives →
Recent activity from HAProxy Kubernetes Ingress Controller and k0s
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
- 5d agok0sk0s opens the 1.37 line with v1.37.1
- 5d agok0s1.36.5: Kubernetes bump, etcd 3.6.15, scoped worker autopilot
- 5d agok0sv1.35.9: Kubernetes, etcd and containerd roll-up
- 5d agok0sv1.34.12: Kubernetes and etcd roll-up
- 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
- 25d agoHAProxy Kubernetes Ingress Controllerv3.2.16: dependency, CI and test maintenance
- 1mo agok0s1.36.4+k0s.1 fixes GHSA-qjgc-wmg7-3jc3
- 1mo agok0s1.35.8+k0s.1 fixes GHSA-qjgc-wmg7-3jc3, hardens csr-approver
- 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 k0s?
They serve adjacent needs but don't currently overlap on shipped themes. HAProxy Kubernetes Ingress Controller and k0s 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 k0s?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HAProxy Kubernetes Ingress Controller and k0s 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 k0s?
Top k0s alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "k0s alternatives" section above for the current picks, or visit /alternatives/k0s for the full list with editorial commentary on each.