Lima
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
Comparison · Infra & APIs
HAProxy Kubernetes Ingress Controller vs Terragrunt
A side-by-side editorial comparison of HAProxy Kubernetes Ingress Controller and Terragrunt — release velocity, themes, recent moves, and the top alternatives to consider.
HAProxy Kubernetes Ingress Controller vs Terragrunt: at a glance
| Feature | HAProxy Kubernetes Ingress Controller | Terragrunt |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | ingress-controller, haproxy, kubernetes, patch-release | terraform, infrastructure-as-code, experiments, release-candidate |
| Last editorial update | 58m ago | 6h ago |
| Website | Visit → | Visit → |
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 Terragrunt?
Terragrunt 1.2's last candidate finishes eleven experiments and locks down state buckets.
Terragrunt v1.2.0-rc3, dated mid-October, is declared the final candidate: unless a blocker appears, v1.2.0 ships with its contents. The cycle completes eleven experiments, among them OCI, block-iteration, azure-backend and optional-hooks. Two changes need attention: base64gzip() now returns the Go 1.27 encoder's output, which can trigger resource replacements, and S3 bootstrapping no longer adds the RootAccess bucket policy statement.
HAProxy Kubernetes Ingress Controller vs Terragrunt: 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.
Terragrunt
5.0INFRA · APIS
Terragrunt 1.2's last candidate finishes eleven experiments and locks down state buckets.
◆ Current state
Terragrunt v1.2.0-rc3, dated mid-October, is declared the final candidate: unless a blocker appears, v1.2.0 ships with its contents. The cycle completes eleven experiments, among them OCI, block-iteration, azure-backend and optional-hooks. Two changes need attention: base64gzip() now returns the Go 1.27 encoder's output, which can trigger resource replacements, and S3 bootstrapping no longer adds the RootAccess bucket policy statement.
◆ Where it's heading
The graduation model has repeated at a larger scale: six experiments in v1.1, eleven in v1.2. The candidates ran as stabilization, with fixes concentrated in the CAS, the catalog and the Provider Cache Server. Each breaking change also ships with an escape hatch, base64gzip_compat() or enable_bucket_root_access, which shows how seriously the project treats its 1.0 guarantees.
◆ Prediction
v1.2.0 final is the next release, since rc3 says only regression or urgent fixes will land first. It has not appeared in this feed in the 18 days since rc3.
Alternatives to HAProxy Kubernetes Ingress Controller and Terragrunt
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 Terragrunt.
Verdaccio
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
Snort 3
Snort 3.12.4 pairs a long memory-safety pass with detection speed work
Honeycomb
Honeycomb is working on the first ten minutes, not just the incident
Talos Linux
Talos 1.15's alpha keeps moving: a silent containerd config trap and declarative CPU control
Apache Pinot
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 Terragrunt alternatives →
Recent activity from HAProxy Kubernetes Ingress Controller and Terragrunt
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
- 12d agoHAProxy Kubernetes Ingress Controllerv3.2.18: keeps all TLS secrets per host, CRD panic fix
- 17d agoTerragruntv1.2.0-rc3: final candidate, nine more bug fixes
- 17d agoHAProxy Kubernetes Ingress Controllerv3.2.17: k8s.io, x/ and client-native dependency updates
- 25d agoTerragruntv1.2.0-rc2: CAS, catalog and provider cache fixes
- 25d agoHAProxy Kubernetes Ingress Controllerv3.2.16: dependency, CI and test maintenance
- 1mo agoTerragruntv1.2.0-rc1 completes eleven experiments at once
- 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 agoTerragruntv1.1.0-rc3
- 4mo agoTerragruntv1.1.0-rc2
- 4mo agoTerragruntv1.1.0-rc1 ⚡
Frequently asked questions
What is the difference between HAProxy Kubernetes Ingress Controller and Terragrunt?
They serve adjacent needs but don't currently overlap on shipped themes. HAProxy Kubernetes Ingress Controller and Terragrunt 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 Terragrunt?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HAProxy Kubernetes Ingress Controller and Terragrunt 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 Terragrunt?
Top Terragrunt alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Terragrunt alternatives" section above for the current picks, or visit /alternatives/terragrunt for the full list with editorial commentary on each.