ClouDNS
ClouDNS widens its SSL catalog and adds maintenance windows to monitoring
A side-by-side editorial comparison of Gloo Gateway and Terragrunt — release velocity, themes, recent moves, and the top alternatives to consider.
Gloo Gateway's October batch fixes proxies that silently kept stale endpoints.
Gloo Gateway still maintains 1.19, 1.20 and 1.21 in parallel and releases them in same-day batches. The 2026-10-21 batch fixes a bug where a placeholder EDS assignment carried the wrong cluster name, so a proxy received an update it could not match, kept its old endpoints and never recovered. Each line also moved to Go 1.26.10; 1.21 additionally upgraded kin-openapi.
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.
Gloo Gateway still maintains 1.19, 1.20 and 1.21 in parallel and releases them in same-day batches. The 2026-10-21 batch fixes a bug where a placeholder EDS assignment carried the wrong cluster name, so a proxy received an update it could not match, kept its old endpoints and never recovered. Each line also moved to Go 1.26.10; 1.21 additionally upgraded kin-openapi.
Releases remain maintenance: Go and Kubernetes bumps on a weekly rhythm, with an occasional real bug fix shipped to every line at once. The 1.18 line no longer appears in the October batches. No new features are visible.
Expect further same-day dependency batches across the three lines; the entries show no feature release coming.
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.
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.
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.
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 Gloo Gateway or Terragrunt.
ClouDNS widens its SSL catalog and adds maintenance windows to monitoring
fossa-cli's feed jumps from 3.17 to 3.20, with clearer container scan errors.
Traefik v3.8 rc.1 is a Gateway API release; v2.11 keeps getting security patches.
Render's autumn changelog is plan tuning and runtime defaults while Workflows fills out.
Home Assistant keeps pulling hidden power-user features into the UI, now trigger IDs.
Alertmanager 0.34.2 turns off CORS by default, breaking cross-origin API calls.
See all Gloo Gateway alternatives → · See all Terragrunt alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Gloo Gateway 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Gloo Gateway 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.
Top Gloo Gateway alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Gloo Gateway alternatives" section above for the current picks, or visit /alternatives/gloo for the full list with editorial commentary on each.
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.