Apptainer
Apptainer 1.6 candidate adds delta images that rebuild only what changed.
A side-by-side editorial comparison of k0s and Terragrunt — release velocity, themes, recent moves, and the top alternatives to consider.
k0s ships another four-branch patch round, with an IPv6 service CIDR fix on 1.37 and 1.36.
On November 3 k0s released v1.37.2, 1.36.6, 1.35.10 and 1.34.13 within minutes of each other. The 1.37 and 1.36 releases remove a size limit on IPv6 service CIDRs and update containerd to 2.3.6; 1.37.2 also bumps kine, ORAS and troubleshoot. The 1.35 and 1.34 branches take only Kubernetes patch updates.
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.
On November 3 k0s released v1.37.2, 1.36.6, 1.35.10 and 1.34.13 within minutes of each other. The 1.37 and 1.36 releases remove a size limit on IPv6 service CIDRs and update containerd to 2.3.6; 1.37.2 also bumps kine, ORAS and troubleshoot. The 1.35 and 1.34 branches take only Kubernetes patch updates.
k0s now maintains four branches on a shared patch cadence, roughly one coordinated round a week after the 1.37 line opened on October 27. Fixes and dependency updates land on the newest two branches, while older ones receive only Kubernetes patches, which indicates where active support is concentrated.
Expect the next coordinated round to follow upstream Kubernetes patch releases, with 1.34 likely to stop receiving updates as 1.37 matures.
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 k0s or Terragrunt.
Apptainer 1.6 candidate adds delta images that rebuild only what changed.
Coder ships the same security backports to three release lines in one afternoon.
Robusta's 0.54.0 alpha returns to features: Prometheus tenants by namespace and Holmes fixes.
ShenYu is cutting 2.7.2 release candidates, but the tags still carry no notes.
Honeycomb's Canvas now remembers your systems and lays out each investigation in sections.
AdGuard Home's stable line takes a Go security update and turns off Multipath TCP.
See all k0s 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. k0s 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. k0s 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 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.
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.