https://blog.k0sproject.io/tags/v2.1.0/Recent content in V2.1.0 on The Zero Friction Kubernetes BlogHugo -- 0.148.2enCopyright © 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.Mon, 10 Aug 2026 09:00:00 +0000https://blog.k0sproject.io/posts/k0smotron-v2.1.0-worker-inplace-upgrades/Mon, 10 Aug 2026 09:00:00 +0000https://blog.k0sproject.io/posts/k0smotron-v2.1.0-worker-inplace-upgrades/<p>k0smotron v2.1.0 is out. Alongside a batch of fixes and dependency bumps, this release closes a gap that&rsquo;s been open for a while: <strong>in-place upgrades, now also available for worker nodes</strong>. Check the <a href="https://github.com/k0sproject/k0smotron/releases/tag/v2.1.0">full changelog</a> for everything included. This post focuses on the in-place upgrade story, where we came from and what changes now.</p> <h2 id="in-place-upgrades-before-v210">In-place upgrades, before v2.1.0</h2> <p>k0smotron has supported in-place upgrades for control plane nodes for a while, through <code>spec.updateStrategy: InPlace</code> on <code>K0sControlPlane</code>. This is a standalone mechanism: the control plane controller detects a k0s version change, builds an autopilot <code>Plan</code> targeting the control plane nodes that require a k0s version update, and lets <a href="https://docs.k0smotron.io/">autopilot</a> roll out the new k0s version without replacing the underlying machine. No CAPI involvement beyond the control plane controller itself.</p>