<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Benchmark on The Zero Friction Kubernetes Blog</title><link>https://blog.k0sproject.io/tags/benchmark/</link><description>Recent content in Benchmark on The Zero Friction Kubernetes Blog</description><generator>Hugo -- 0.148.2</generator><language>en</language><copyright>Copyright © 2023 k0sproject a Series of LF Projects, LLC. For website terms of use, trademark policy and other project policies please see Linux Foundation policies. - All rights reserved.</copyright><lastBuildDate>Tue, 05 May 2026 10:13:18 +0300</lastBuildDate><atom:link href="https://blog.k0sproject.io/tags/benchmark/index.xml" rel="self" type="application/rss+xml"/><item><title>The k0smotron Big Bang Benchmark</title><link>https://blog.k0sproject.io/posts/k0smotron-big-bang-benchmark/</link><pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate><guid>https://blog.k0sproject.io/posts/k0smotron-big-bang-benchmark/</guid><description>&lt;p>With k0smotron, every workload cluster gets a Kubernetes control plane that runs as pods inside a management cluster.
Hosted control planes (HCPs) become ordinary Kubernetes workloads: schedulable, patchable, killable like any other
Deployment.&lt;/p>
&lt;p>The tradeoff is that the management cluster pays the bill. Ten HCPs cost almost nothing. A hundred is a different story.
Storage backends, pod limits, watch delivery, and k0smotron reconciliation all start to matter at the same time, and the
question is which one cracks first.&lt;/p></description></item></channel></rss>