Lima
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
A side-by-side editorial comparison of HAProxy Kubernetes Ingress Controller and Tekton Pipelines — release velocity, themes, recent moves, and the top alternatives to consider.
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 →
Tekton 1.18 LTS lets a Task finish its steps and still fail.
v1.18.0, an LTS release, adds continueAndFail for step.onError: remaining steps run, then the TaskRun fails. Controller-managed labels become immutable through the webhook, and a truncation bug in large OCI-resolved bundles is fixed. On October 23 five maintained branches, from v1.6.x to v1.17.x, received the same Go 1.27.3 image bump, and v1.6, v1.9 and v1.12 also got a vendor tarball fix.
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.
v1.18.0, an LTS release, adds continueAndFail for step.onError: remaining steps run, then the TaskRun fails. Controller-managed labels become immutable through the webhook, and a truncation bug in large OCI-resolved bundles is fixed. On October 23 five maintained branches, from v1.6.x to v1.17.x, received the same Go 1.27.3 image bump, and v1.6, v1.9 and v1.12 also got a vendor tarball fix.
This cycle is quieter than the security-context change in v1.16. New capability is small and aimed at real pipeline behavior, such as collecting all test results before failing, while most of the release effort goes to keeping many branches current. Making labels immutable fits the same theme as v1.16: tightening what users can change on objects the controller owns.
Expect more same-day patch sets across the LTS branches, since that pattern now repeats. No further end-of-life move appears in these entries, so timing for retiring older branches is unclear.
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 Tekton Pipelines.
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
Snort 3.12.4 pairs a long memory-safety pass with detection speed work
Honeycomb is working on the first ten minutes, not just the incident
Talos 1.15's alpha keeps moving: a silent containerd config trap and declarative CPU control
Pinot 1.6 adds SQL DDL and vector backends, and now needs Java 25 to run its services.
See all HAProxy Kubernetes Ingress Controller alternatives → · See all Tekton Pipelines alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — kubernetes — within Infra & APIs. HAProxy Kubernetes Ingress Controller and Tekton Pipelines 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. HAProxy Kubernetes Ingress Controller and Tekton Pipelines 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 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.
Top Tekton Pipelines alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Tekton Pipelines alternatives" section above for the current picks, or visit /alternatives/tekton for the full list with editorial commentary on each.