Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
Comparison · Infra & APIs
Gitness vs k0s
A side-by-side editorial comparison of Gitness and k0s — release velocity, themes, recent moves, and the top alternatives to consider.
Gitness vs k0s: at a glance
What is Gitness?
Harness Open Source last shipped in August 2025, on this feed at least
The feed holds two releases of Harness Open Source, tracked here as Gitness. v3.2.0 in May 2025 added Git LFS, default reviewers through branch rules and a Revert PR option; v3.3.0 that August added tag rules, a PR dashboard upgrade with favourite repositories, and a fix for a Git LFS upload path flaw. Nothing newer appears here.
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.
Gitness vs k0s: editorial side-by-side
Gitness
0.0INFRA · APIS
Harness Open Source last shipped in August 2025, on this feed at least
◆ Current state
The feed holds two releases of Harness Open Source, tracked here as Gitness. v3.2.0 in May 2025 added Git LFS, default reviewers through branch rules and a Revert PR option; v3.3.0 that August added tag rules, a PR dashboard upgrade with favourite repositories, and a fix for a Git LFS upload path flaw. Nothing newer appears here.
◆ Where it's heading
Both releases deepen code-hosting governance: branch rules, then tag rules, plus review routing through Code Owners. That is parity work against established Git hosts rather than a new direction. With entries more than a year old, the feed shows where the project was heading in 2025, not where it is now.
◆ Prediction
The entries do not support a confident call: there is no release in this feed after v3.3.0, so it is unclear whether the project slowed or the feed stopped tracking it.
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 Gitness 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 Gitness 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.
Recent activity from Gitness and k0s
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 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
- 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
- 1y agoGitnessHarness Open Source 3.3: tag rules, PR dashboard, LFS path fix
- 1y agoGitnessHarness Open Source 3.2: Git LFS, default reviewers, Revert PR
Frequently asked questions
What is the difference between Gitness and k0s?
They serve adjacent needs but don't currently overlap on shipped themes. k0s is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Gitness better than k0s?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. k0s is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Gitness?
Top Gitness alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Gitness alternatives" section above for the current picks, or visit /alternatives/gitness 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.