<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Kairos Blog</title>
        <link>https://kairos.io/blog/</link>
        <description>Kairos Blog</description>
        <lastBuildDate>Mon, 31 Aug 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[One Repo, One Pipeline, One Version]]></title>
            <link>https://kairos.io/blog/2026/08/31/one-repo-one-pipeline-one-version/</link>
            <guid>https://kairos.io/blog/2026/08/31/one-repo-one-pipeline-one-version/</guid>
            <pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[kairos-agent, immucore, kairos-sdk, kairos-init, and kcrypt-discovery-challenger have moved into kairos-io/kairos. Why we did it, what the new build pipeline looks like, and what actually happens to five repos' worth of git history.]]></description>
            <content:encoded><![CDATA[<p>If you've built Kairos from source in the last few days, you've noticed: <code>kairos-agent</code>, <code>immucore</code>, <code>kairos-sdk</code>, <code>kairos-init</code>, and <code>kcrypt-discovery-challenger</code> are gone. Not deleted. Moved. They now live inside <a href="https://github.com/kairos-io/kairos" target="_blank" rel="noopener noreferrer" class="">kairos-io/kairos</a>, as <code>agent/</code>, <code>immucore/</code>, <code>sdk/</code>, <code>kairos-init/</code>, and <code>kcrypt/</code>.</p>
<p><strong>TL;DR, if you just need to keep building:</strong></p>
<ul>
<li class="">The five repos are archived, not deleted. Their code, full git history, and existing published tags all still work. Receipts at the bottom if you want them.</li>
<li class="">Using the SDK: import <code>github.com/kairos-io/kairos/sdk/...</code> (e.g. <code>sdk/bus</code>, <code>sdk/collector</code>, <code>sdk/machine</code>) instead of <code>github.com/kairos-io/kairos-sdk</code>. Code pinned to old <code>kairos-sdk</code> tags keeps building unchanged.</li>
<li class="">Using kairos-init, kairos-agent, immucore, kcrypt-discovery-challenger: same binaries, same container images, same tag pattern, just built from the monorepo now, versioned off <code>kairos-io/kairos</code>'s own tag instead of their own.</li>
<li class="">Their next release will jump from their own <code>v0.x</code> / <code>v2.x</code> number straight to the shared <code>v4.x.x</code> line. That is <strong>not</strong> a wall of breaking changes compressed into one release. See "About that version jump" at the bottom before you panic.</li>
<li class="">The SDK doesn't get this jump at all: it's not an independently tagged artifact anymore, so there's no "next sdk version" to be surprised by. Details below.</li>
</ul>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-problem-this-actually-solves">The problem this actually solves<a href="https://kairos.io/blog/2026/08/31/one-repo-one-pipeline-one-version/#the-problem-this-actually-solves" class="hash-link" aria-label="Direct link to The problem this actually solves" title="Direct link to The problem this actually solves" translate="no">​</a></h2>
<p>Kairos has never shipped as a single thing. A user running Ubuntu Kairos 3.5 was told to move to kairos-init 2.6. Running <code>--version</code> on the agent gave 2.2. Three numbers, one product, and no way to tell which of them was "your" version.</p>
<p>That wasn't a labeling problem. It was a real coordination cost. <code>kairos-init</code> alone was maintaining four minor lines at once in July, because each one tracked a different Kairos release under the hood. The mapping between components already existed; only maintainers could read it. We <a href="https://github.com/kairos-io/kairos/issues/4301" target="_blank" rel="noopener noreferrer" class="">wrote up the case for a single shared version number</a> in detail, and partway through that discussion the obvious question came up: why keep the mapping in a table at all, when the fix is to stop having five things to map between?</p>
<p>So: monorepo. Not because monorepos are fashionable, but because it's the most direct way to make "one version" mechanically true instead of a promise five release pipelines have to keep independently.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-actually-moved-and-how">What actually moved, and how<a href="https://kairos.io/blog/2026/08/31/one-repo-one-pipeline-one-version/#what-actually-moved-and-how" class="hash-link" aria-label="Direct link to What actually moved, and how" title="Direct link to What actually moved, and how" translate="no">​</a></h2>
<p>Each component came in with <a href="https://github.com/kairos-io/kairos/commit/1b6014b33929163a64ccad5fdf242a0a70bd7d70" target="_blank" rel="noopener noreferrer" class=""><code>git subtree add</code></a>, one PR per component: <a href="https://github.com/kairos-io/kairos/pull/4343" target="_blank" rel="noopener noreferrer" class="">kairos-sdk</a>, then <a href="https://github.com/kairos-io/kairos/pull/4344" target="_blank" rel="noopener noreferrer" class="">agent, immucore, kairos-init, and kcrypt together</a>. The five source repos are archived, with a banner pointing here.</p>
<p>Nothing published from them stops working. Every Go module tag (<code>go get github.com/kairos-io/kairos-agent/v2@v2.31.1</code>) still resolves through the Go module proxy forever, because the proxy caches it independently of the source repo's state. Every container tag on <code>quay.io</code> stays pullable. Archived just means read-only on GitHub, not gone.</p>
<p><strong>Why these five, and not repos like <code>AuroraBoot</code> or <code>kairos-operator</code>?</strong> Because these five never actually had a release cadence of their own to protect. Every one of them released to serve a specific Kairos release, not on a schedule that made sense by itself. During v4.2.0's RC cycle alone (August 10 to August 18), <code>kairos-agent</code> shipped four releases: <code>v2.31.1</code> the day RC1 went out, <code>v2.31.4</code> the day the final tag did. That's not a library with its own users on its own timeline. That's the same release, wearing a second number.</p>
<p><code>AuroraBoot</code> and <code>kairos-operator</code> are different in kind, not degree. They shipped zero releases during that same eight-day window, both last touched before the RC cycle even started, both went on to release again afterward without a new Kairos tag anywhere nearby. People build with them independently of whether Kairos itself shipped anything new that week. Folding them in would take away a cadence they actually use, so they stayed where they are.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-pipeline-finally-looks-like-one">The pipeline finally looks like one<a href="https://kairos.io/blog/2026/08/31/one-repo-one-pipeline-one-version/#the-pipeline-finally-looks-like-one" class="hash-link" aria-label="Direct link to The pipeline finally looks like one" title="Direct link to The pipeline finally looks like one" translate="no">​</a></h2>
<p>This is the part we're most glad to be rid of. Before the move, a change to Kairos touched up to six separate CI systems that didn't know about each other: <code>kairos</code>'s own <code>binaries.yaml</code>, <code>image-master*.yaml</code>, <code>uki.yaml</code>, <code>lint.yaml</code>, and <code>unit-tests.yaml</code>, plus whatever each of <code>kairos-agent</code>, <code>immucore</code>, <code>kairos-sdk</code>, <code>kairos-init</code>, and <code>kcrypt-discovery-challenger</code> ran on their own. A red build in <code>kairos-init</code> didn't stop a green <code>kairos</code> release from shipping against it. Finding out <em>why</em> something broke meant checking six Actions tabs.</p>
<p><code>master.yaml</code> retires all five of the <code>kairos</code>-side files above and replaces them with one dependency graph:</p>
<div class="language-text codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-text codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token plain">unit-tests, lint, build-binaries</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        └──▶ build-images</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">                  ├──▶ build-iso        ──▶ qemu-tests-core / -standard / -uki</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">                  └──▶ build-iso-arm            │</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">                                                 ▼</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">                                          promote-images</span><br></div></code></pre></div></div>
<p>Here's a run of it, in progress:</p>
<p><img decoding="async" loading="lazy" src="https://github.com/user-attachments/assets/a924f4d6-8a23-4ec7-91b8-33540cf086ca" alt="Kairos master.yaml pipeline graph" class="img_ev3q"></p>
<p>The safety property is the part that's easy to miss looking at the graph: <code>build-images</code> doesn't push straight to <code>:master</code>. It pushes to <code>:master-scratch</code>, the ISO and qemu jobs test <em>that</em>, and only <code>promote-images</code> (after every qemu job is green, arm build included) copies the manifest across to <code>:master</code>. A broken push leaves <code>:master-scratch</code> broken and <code>:master</code> untouched, instead of shipping a red build to the tag everything else pulls from.</p>
<p>The tag-triggered <code>release.yaml</code> mirrors the same shape for <code>v*</code> tags: scratch tag, qemu-gate, promote to the release tag and <code>:latest</code>, then attach binary archives to the GitHub Release. One honest gap: <code>release-legacy.yaml</code> still runs alongside it for now, because it builds a k3s/k0s per-version ISO matrix the new pipeline doesn't produce yet. That's a tracked follow-up, not a silent omission.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-things-get-released-concretely">Where things get released, concretely<a href="https://kairos.io/blog/2026/08/31/one-repo-one-pipeline-one-version/#where-things-get-released-concretely" class="hash-link" aria-label="Direct link to Where things get released, concretely" title="Direct link to Where things get released, concretely" translate="no">​</a></h2>
<p>One tag on <code>kairos-io/kairos</code>, e.g. <code>v4.3.0</code>, now produces everything: the <code>kairos-agent</code>, <code>immucore</code>, <code>kcrypt-discovery-challenger</code>, <code>provider-kairos</code>, and <code>kairos-installer</code> binaries, plus <code>kairos-init</code>, all built from <code>VERSION := git describe --tags</code>, all linked with the same <code>-X .../internal/version.Version=$(VERSION)</code>. Every one of them reports <code>v4.3.0</code> when you ask. That's <a href="https://github.com/kairos-io/kairos/issues/4301" target="_blank" rel="noopener noreferrer" class="">#4301</a>'s ask, done: not as a policy anyone has to remember to follow, but as a Makefile variable everything shares because it's now one <code>git describe</code> away.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="about-that-version-jump">About that version jump<a href="https://kairos.io/blog/2026/08/31/one-repo-one-pipeline-one-version/#about-that-version-jump" class="hash-link" aria-label="Direct link to About that version jump" title="Direct link to About that version jump" translate="no">​</a></h2>
<p>If you build your own images, four components are about to jump straight to the shared <code>v4.x.x</code> line, all at once:</p>
<table><thead><tr><th>Component</th><th>Current standalone version</th><th>Next release</th></tr></thead><tbody><tr><td><code>kairos-agent</code></td><td><code>v2.31.4</code></td><td><code>v4.x.x</code></td></tr><tr><td><code>immucore</code></td><td><code>v0.20.4</code></td><td><code>v4.x.x</code></td></tr><tr><td><code>kairos-init</code></td><td><code>v0.16.3</code></td><td><code>v4.x.x</code></td></tr><tr><td><code>kcrypt-discovery-challenger</code></td><td><code>v0.13.4</code></td><td><code>v4.x.x</code></td></tr></tbody></table>
<p>On their own, those numbers look like a scare jump: two, or four, majors in one bump usually means "expect everything to be different." It doesn't mean that here. It's the same code, the same maintainers, the same review process, doing what would otherwise have shipped as <code>v2.32.0</code> or <code>v0.16.4</code> or <code>v0.13.5</code> under each component's old numbering, just carrying the shared Kairos version instead of its own independent one, for exactly the reason in the first section: so nobody has to keep a private table mapping <code>immucore 0.20.4</code> to <code>Kairos 4.2.0</code> in their head. Check the changelog for what actually changed, not the size of the version jump. The jump itself carries no compatibility signal, this once.</p>
<p><strong>The SDK is a different case, and doesn't get a version jump at all.</strong> <code>kairos-sdk</code> was already a <code>v0.x</code> Go module with no independent artifact beyond its module tag: no container image, no release binary. Now that <code>sdk/</code> is a plain subpackage of <code>github.com/kairos-io/kairos</code>, it has no version of its own to bump: you pin the whole <code>kairos</code> module (<code>go get github.com/kairos-io/kairos@v4.3.0</code>) and the SDK code comes along at whatever that resolves to. There's no <code>kairos-sdk v4.x.x</code> release to look out for, because <code>kairos-sdk</code> as a separately versioned thing stops existing at this move, not just at this jump.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="try-it">Try it<a href="https://kairos.io/blog/2026/08/31/one-repo-one-pipeline-one-version/#try-it" class="hash-link" aria-label="Direct link to Try it" title="Direct link to Try it" translate="no">​</a></h2>
<p>Clone <code>kairos-io/kairos</code>, and <code>agent/</code>, <code>immucore/</code>, <code>sdk/</code>, <code>kairos-init/</code>, and <code>kcrypt/</code> are all right there, building from the same <code>go.mod</code>. If something looks wrong, the tracking issue is <a href="https://github.com/kairos-io/kairos/issues/4301" target="_blank" rel="noopener noreferrer" class="">#4301</a> and the pipeline work is ongoing in the open. Come poke at it.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="does-the-git-history-survive">Does the git history survive?<a href="https://kairos.io/blog/2026/08/31/one-repo-one-pipeline-one-version/#does-the-git-history-survive" class="hash-link" aria-label="Direct link to Does the git history survive?" title="Direct link to Does the git history survive?" translate="no">​</a></h2>
<p>Least important part of this story if you just build against Kairos, but we checked rather than assumed, so here's the receipt. Short answer: yes, but with one real wrinkle worth knowing about.</p>
<p><code>git subtree add</code> grafts the entire source repo as a second parent of the merge commit. It doesn't rewrite or truncate anything. We verified this per component by walking the ancestry of the commit each subtree merge points at:</p>
<table><thead><tr><th>Component</th><th>Commits in the original repo</th><th>Commits reachable from the graft point</th></tr></thead><tbody><tr><td><code>kairos-agent</code> → <code>agent/</code></td><td>2,031</td><td>2,030</td></tr><tr><td><code>immucore</code> → <code>immucore/</code></td><td>648</td><td>645</td></tr><tr><td><code>kairos-sdk</code> → <code>sdk/</code></td><td>922</td><td>921</td></tr><tr><td><code>kairos-init</code> → <code>kairos-init/</code></td><td>505</td><td>504</td></tr><tr><td><code>kcrypt-discovery-challenger</code> → <code>kcrypt/</code></td><td>347</td><td>344</td></tr></tbody></table>
<p>(The handful missing per component are the "add archive notice" commits made on each repo after the graft, nothing from before it.) Every one of those commits is a real, permanent, unreachable-by-<code>git gc</code> part of <code>kairos-io/kairos</code>'s history now.</p>
<p><code>git blame</code> finds it without help. Blame a line in <code>agent/internal/agent/agent.go</code> today and it correctly walks past the merge into <code>kairos-agent</code>'s original commit from 2022, author and all.</p>
<p>The wrinkle: <code>git log -- agent/some/file.go</code> does <em>not</em> walk through automatically. <code>git subtree add</code> merges the foreign tree in at a prefix; it doesn't rewrite the foreign history's paths to match, so git's default path-history simplification (which drives <code>git log &lt;path&gt;</code> and GitHub's "History" button on a file) doesn't connect the two sides on its own. If you want the pre-move commit log for something now under <code>agent/</code>, go to the graft commit directly:</p>
<div class="language-sh codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-sh codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">git</span><span class="token plain"> log 14f0d3bf68b60c86efbfd1dd857a0d9087bac7b1 -- some/file.go</span><br></div></code></pre></div></div>
<p>(Swap in the commit named in <code>agent/</code>'s "Add 'agent/' from commit '...'" merge: <a href="https://github.com/kairos-io/kairos/commit/00b8fb5c11595dc019be749293222be920cb3155" target="_blank" rel="noopener noreferrer" class="">immucore</a>, <a href="https://github.com/kairos-io/kairos/commit/1b6014b33929163a64ccad5fdf242a0a70bd7d70" target="_blank" rel="noopener noreferrer" class="">sdk</a>, <a href="https://github.com/kairos-io/kairos/commit/108c45182d318da0c118513e4b3567f021380b04" target="_blank" rel="noopener noreferrer" class="">kairos-init</a>, <a href="https://github.com/kairos-io/kairos/commit/eb51205c693c09bbd7f3db8e8295abc8128637b1" target="_blank" rel="noopener noreferrer" class="">kcrypt</a> each have their own.) Or just clone the archived repo. It isn't going anywhere either.</p>
<p>So: nothing was lost. Something did get a little harder to find, and now you know where to look.</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Kairos on RISC-V: An Open Invitation to Test It]]></title>
            <link>https://kairos.io/blog/2026/08/28/kairos-riscv64-open-invitation/</link>
            <guid>https://kairos.io/blog/2026/08/28/kairos-riscv64-open-invitation/</guid>
            <pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[An open invitation to the RISC-V community to help test Kairos on riscv64, plus everything you need to get an image running and installed.]]></description>
            <content:encoded><![CDATA[<p>Dear community,</p>
<p>For the past few months I've been working on RISC-V support for Kairos. I think this is a very exciting technology and one where I'd enjoy seeing the easy lifecycle management that Kairos brings paired with. In this post you'll see an emulated k3s cluster on an Ubuntu 24.04 Kairos image. I think it's time to get out of the VM, and here's where you come in. If you have a RISC-V board, I'd like to invite you to do some testing to help us run on metal.</p>
<!-- -->
<p>I've teased the progress a few times, but I never had anything concrete to actually show, until now. I want you to keep an open mind. This is a work in progress, and there are probably more rough edges than I'd like.</p>
<p><img decoding="async" loading="lazy" alt="Terminal showing a Kairos riscv64 system booted on Ubuntu 24.04, with kubectl get nodes reporting the node Ready as control-plane, running k3s v1.36.3" src="https://kairos.io/assets/images/kairos-riscv64-k3s-ready-c691aa5cef8554e694731970c6d66edd.png" width="2104" height="1484" class="img_ev3q"></p>
<p>As you can see, this is a Kairos system based on Ubuntu 24.04, running k3s, on riscv64. Exciting, but it's way too soon to call victory: none of this has been tested on real hardware yet. Report what breaks, and we'll work through the fixes together.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-things-stand">Where things stand<a href="https://kairos.io/blog/2026/08/28/kairos-riscv64-open-invitation/#where-things-stand" class="hash-link" aria-label="Direct link to Where things stand" title="Direct link to Where things stand" translate="no">​</a></h2>
<p>The Ubuntu base comes straight from upstream. k3s comes from <a href="https://github.com/CARV-ICS-FORTH/k3s" target="_blank" rel="noopener noreferrer" class="">CARV-ICS-FORTH's actively-maintained riscv64 fork</a>, since k3s has no official riscv64 release yet. There's an open upstream ticket to change that: <a href="https://github.com/k3s-io/k3s/issues/7151" target="_blank" rel="noopener noreferrer" class="">k3s-io/k3s#7151</a>. The same is true for k0s: <a href="https://github.com/k0sproject/k0s/issues/1919" target="_blank" rel="noopener noreferrer" class="">k0sproject/k0s#1919</a>. One way to help without touching any hardware: go show interest on those tickets, it moves us closer to official releases.</p>
<p>Worth mentioning too: <a href="https://kairos.io/blog/2025/12/17/introducing-hadron-the-minimal-upstream-first-linux-base-for-kairos/" target="_blank" rel="noopener noreferrer" class="">Hadron</a>, the minimal, upstream-first base Kairos is moving toward, already builds and passes its own tests on riscv64 in CI. There's just no public release with it yet.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="downloading-the-system-image">Downloading the system image<a href="https://kairos.io/blog/2026/08/28/kairos-riscv64-open-invitation/#downloading-the-system-image" class="hash-link" aria-label="Direct link to Downloading the system image" title="Direct link to Downloading the system image" translate="no">​</a></h2>
<p>A quick note before you download: this isn't an official Kairos release. Kairos officially only ships Hadron-based images today, and as I mentioned, there's no official riscv64 support yet either. On top of that, the unofficial k3s build needs a few hacks bolted onto the normal <code>kairos-init</code> flow that aren't going to land in <code>kairos-init</code> itself. So for now, this image lives on my own personal repo, not an official Kairos channel.</p>
<p>Download the ISO from the <a href="https://github.com/mauromorales/homelab/releases/tag/kairos-riscv64-v0.1.3" target="_blank" rel="noopener noreferrer" class="">latest release</a>. Boot it (<code>qemu-system-riscv64</code>, or real riscv64 hardware if you have it) and tell me if and where it breaks, with as much detail as you can give me. We'll work through a fix together, and you can help me keep testing from there.</p>
<p>The raw disk image (for flashing straight to hardware, no installer step) is too big for a GitHub release asset, so it's published as a scratch OCI image on Quay instead:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token builtin class-name">export</span><span class="token plain"> </span><span class="token assign-left variable" style="color:#36acaa">IMAGE</span><span class="token operator" style="color:#393A34">=</span><span class="token plain">quay.io/mauromorales/kairos-riscv64:0.1.3-img</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token assign-left variable" style="color:#36acaa">container</span><span class="token operator" style="color:#393A34">=</span><span class="token variable" style="color:#36acaa">$(</span><span class="token variable function" style="color:#d73a49">docker</span><span class="token variable" style="color:#36acaa"> create </span><span class="token variable string" style="color:#e3116c">"</span><span class="token variable string variable" style="color:#36acaa">$IMAGE</span><span class="token variable string" style="color:#e3116c">"</span><span class="token variable" style="color:#36acaa"> noop</span><span class="token variable" style="color:#36acaa">)</span><span class="token plain">   </span><span class="token comment" style="color:#999988;font-style:italic"># scratch image, never executed</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">docker</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">cp</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"</span><span class="token string variable" style="color:#36acaa">$container</span><span class="token string" style="color:#e3116c">:/output/."</span><span class="token plain"> </span><span class="token builtin class-name">.</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">docker</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">rm</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"</span><span class="token string variable" style="color:#36acaa">$container</span><span class="token string" style="color:#e3116c">"</span><br></div></code></pre></div></div>
<p>That's it. Now you should have an image to test on your device.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="if-your-device-boots-successfully">If your device boots successfully<a href="https://kairos.io/blog/2026/08/28/kairos-riscv64-open-invitation/#if-your-device-boots-successfully" class="hash-link" aria-label="Direct link to If your device boots successfully" title="Direct link to If your device boots successfully" translate="no">​</a></h2>
<p>The next step is to actually install Kairos. I've left a very basic <a href="https://github.com/mauromorales/homelab/blob/main/nodes/kairos-riscv64/cloud-config.yaml" target="_blank" rel="noopener noreferrer" class="">cloud-config</a> you can use as a starting point, but feel free to write your own, backed by the <a href="https://kairos.io/docs/reference/configuration" target="_blank" rel="noopener noreferrer" class="">Kairos configuration reference</a>.</p>
<p>You can install it manually with the agent:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token plain">kairos-agent manual-install </span><span class="token parameter variable" style="color:#36acaa">--device</span><span class="token plain"> auto path/to/your/cloud-config.yaml</span><br></div></code></pre></div></div>
<p>Then shut down and make sure the CD isn't mounted, if that's how you installed. The next time the system boots, it shouldn't show the installer option on GRUB anymore, and your system should be installed.</p>
<p>Open issues on <a href="https://github.com/kairos-io/kairos" target="_blank" rel="noopener noreferrer" class="">kairos-io/kairos</a>, and I'll address them directly with you. If what you hit is actually about k3s or k0s themselves, rather than Kairos, open it upstream instead: <a href="https://github.com/k3s-io/k3s/issues/7151" target="_blank" rel="noopener noreferrer" class="">k3s-io/k3s#7151</a> or <a href="https://github.com/k0sproject/k0s/issues/1919" target="_blank" rel="noopener noreferrer" class="">k0sproject/k0s#1919</a>.</p>
<p>Thanks!</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Kairos v4.2.0: In-Memory Boot, MaaS Support, and Hadron Extension Layers]]></title>
            <link>https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/</link>
            <guid>https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/</guid>
            <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Kairos v4.2.0 adds RAM-only boot with persistent OEM/user storage, the first Hadron extension layers, MaaS support, and initial NVIDIA DGX Spark support, alongside a Hadron STIG hardening baseline and progress on confidential computing.]]></description>
            <content:encoded><![CDATA[<p>Kairos v4.2.0 is now available.</p>
<p>This release opens up new places to run Kairos and new ways to extend it: <strong>boot entirely from RAM</strong> while still keeping persistent config and data on disk, deploy through <strong>Canonical MaaS</strong>, and extend Hadron images with the first <strong>extension layers</strong>. It also brings initial <strong>NVIDIA DGX Spark</strong> support, a hardening baseline for Hadron, and steady progress on confidential computing.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="boot-entirely-from-ram">Boot entirely from RAM<a href="https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/#boot-entirely-from-ram" class="hash-link" aria-label="Direct link to Boot entirely from RAM" title="Direct link to Boot entirely from RAM" translate="no">​</a></h2>
<p>Kairos can now boot with its root filesystem copied entirely into RAM, so nothing on the boot disk is touched at runtime — closer to how ESXi boots than to a typical live CD, but with persistent state still available if you want it.</p>
<p>It's enabled with the <code>kairos.ram</code> boot parameter. On its own, that's a fully diskless boot. Add-on flags let you keep real <code>COS_OEM</code> and <code>COS_PERSISTENT</code> partitions on disk, so configuration and user data survive a reboot even though the OS itself runs from memory:</p>
<ul>
<li class=""><code>kairos.ram.create_partitions[=/dev/sdX]</code> — provision OEM/persistent partitions on first boot</li>
<li class=""><code>kairos.ram.wipe</code> — explicit consent to touch a disk that has foreign partitions on it</li>
<li class=""><code>kairos.ram.oem=&lt;MiB&gt;</code> / <code>kairos.ram.persistent=&lt;MiB&gt;</code> — size the partitions</li>
</ul>
<p>This is aimed at appliances and edge nodes where you want zero disk wear and a boot that's effectively a fresh, known-good state every time, without giving up persistent configuration. It shipped across <code>kairos-sdk</code> (in-RAM detection) and <code>immucore</code> (the boot workflow itself, plus a clearer failure screen if something goes wrong), and it's documented in the <a href="https://kairos.io/docs/installation/netboot" target="_blank" rel="noopener noreferrer" class="">netboot guide</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-first-hadron-extension-layers">The first Hadron extension layers<a href="https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/#the-first-hadron-extension-layers" class="hash-link" aria-label="Direct link to The first Hadron extension layers" title="Direct link to The first Hadron extension layers" translate="no">​</a></h2>
<p>Hadron images can now be extended with <strong>extension layers</strong>: official packages and host-bound components — think firmware, kernel modules, things that don't belong as generic OS packages — delivered either as <strong>sysexts</strong> you can add or remove at runtime without rebuilding the image, or as <strong>build-time layers</strong> baked in when the image is built.</p>
<p>The layers themselves live in <a href="https://github.com/kairos-io/hadron-layers" target="_blank" rel="noopener noreferrer" class="">hadron-layers</a> (currently <code>drbd</code>, <code>fwupd</code>, <code>git</code>, and <code>gpg</code>), with a matching <code>hadron-firmware</code> repo for firmware. They're published as OCI images and listed on <a href="https://hadron-linux.io/components/" target="_blank" rel="noopener noreferrer" class="">hadron-linux.io/components</a>.</p>
<p>This is the first version of the system, and we're treating it as <strong>experimental</strong>: try it, and tell us what layers you need. Community-contributed layers are the direction we want to take this next.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="maas-support">MaaS support<a href="https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/#maas-support" class="hash-link" aria-label="Direct link to MaaS support" title="Direct link to MaaS support" translate="no">​</a></h2>
<p>Kairos now supports deployment through <strong>Canonical MaaS (Metal as a Service)</strong>, with a dedicated MaaS data source for pulling configuration during provisioning. If you already manage bare metal through MaaS, you can bring Kairos into that same workflow instead of running a separate provisioning path for it. See the <a href="https://kairos.io/docs/installation/maas" target="_blank" rel="noopener noreferrer" class="">MaaS installation guide</a> for setup.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="nvidia-dgx-spark-support">NVIDIA DGX Spark support<a href="https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/#nvidia-dgx-spark-support" class="hash-link" aria-label="Direct link to NVIDIA DGX Spark support" title="Direct link to NVIDIA DGX Spark support" translate="no">​</a></h2>
<p>Kairos adds initial support for <strong>NVIDIA DGX Spark</strong> boards (GB10 Grace-Blackwell), including bundled signing keys, board-specific console options, and package mappings in <code>kairos-init</code>.</p>
<p>This lands alongside a broader cleanup of how Kairos builds NVIDIA images: AuroraBoot now emits individual partition images for flashing directly, replacing per-board custom scripts with one standard flow — the same work that already made building for boards like the AGX Orin more uniform. See the <a href="https://kairos.io/docs/installation/nvidia_dgx_spark" target="_blank" rel="noopener noreferrer" class="">DGX Spark build guide</a> for the steps.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-hardening-baseline-for-hadron">A hardening baseline for Hadron<a href="https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/#a-hardening-baseline-for-hadron" class="hash-link" aria-label="Direct link to A hardening baseline for Hadron" title="Direct link to A hardening baseline for Hadron" translate="no">​</a></h2>
<p>Hadron images now ship a real STIG-inspired hardening baseline: an sshd configuration drop-in, around 30 sysctl settings aligned with GPOS guidance, SYN cookies enabled by default, a blocklist for legacy network-protocol kernel modules, and tightened <code>login.defs</code> (password aging, UMASK, login logging).</p>
<p>This is a baseline, not full STIG compliance — PAM hardening (password complexity, history, <code>pam_wheel</code>) and a few other findings didn't make it into this release, and are left for derivative images and your own cloud-config to add on top.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="confidential-computing-real-progress-not-there-yet-on-hadron">Confidential computing: real progress, not there yet on Hadron<a href="https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/#confidential-computing-real-progress-not-there-yet-on-hadron" class="hash-link" aria-label="Direct link to Confidential computing: real progress, not there yet on Hadron" title="Direct link to Confidential computing: real progress, not there yet on Hadron" translate="no">​</a></h2>
<p>Confidential computing support without Hadron is done and documented in this release. Getting it working on Hadron itself is a separate, harder problem: our Hadron-built kernel doesn't currently boot under AMD SEV-SNP, and we haven't been able to pin down why on cloud VMs alone. We're actively trying to get our hands on dedicated SEV-SNP-capable bare metal to debug it properly. If you have access to hardware like this and want to help, reach out — this is exactly the kind of thing that needs a real machine, not another cloud VM.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="cloud-config-changes">Cloud-config changes<a href="https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/#cloud-config-changes" class="hash-link" aria-label="Direct link to Cloud-config changes" title="Direct link to Cloud-config changes" translate="no">​</a></h2>
<p>Two smaller but useful additions to what you can do in a Kairos cloud-config:</p>
<ul>
<li class=""><strong>Templating for <code>config_url</code></strong> — the URL Kairos fetches its config from at boot can now use templating, useful when the same image needs to resolve a different config per machine.</li>
<li class=""><strong><code>gid</code> for users</strong> — you can now specify a group ID alongside a user, not just the username and UID.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="kairos-v3-reaches-end-of-life">Kairos v3 reaches end of life<a href="https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/#kairos-v3-reaches-end-of-life" class="hash-link" aria-label="Direct link to Kairos v3 reaches end of life" title="Direct link to Kairos v3 reaches end of life" translate="no">​</a></h2>
<p>With this release, we've also retired the last Kairos v3 documentation still published on the site (<code>v3.7.2</code>) — see <a href="https://github.com/kairos-io/kairos-docs/pull/668" target="_blank" rel="noopener noreferrer" class="">kairos-docs#668</a>. We keep the latest patch of the three most recent major.minor lines, and v4.2.0 pushes v3 out of that window. If you're still running a v3.x deployment, now is a good time to plan your upgrade to v4.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="and-more">And more<a href="https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/#and-more" class="hash-link" aria-label="Direct link to And more" title="Direct link to And more" translate="no">​</a></h2>
<p>This release also includes a long tail of fixes worth knowing about if you're upgrading: manual-partition sizing now checks against the disk's actual size, control planes are sorted first during node upgrades even without a node selector, AuroraBoot's reported image size is corrected, a user-UID regression is fixed, duplicate extra-partition handling between ISO and user-data sources is resolved, and unformatted extra-partitions no longer fail with an "unsupported filesystem type" error. Reading directly from <code>/etc/elemental/config.yaml</code> is now deprecated.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="looking-ahead">Looking ahead<a href="https://kairos.io/blog/2026/08/18/kairos-v4-2-0-in-memory-boot-maas-extension-layers/#looking-ahead" class="hash-link" aria-label="Direct link to Looking ahead" title="Direct link to Looking ahead" translate="no">​</a></h2>
<p>Kairos v4.2.0 is about giving you more ways to run Kairos and more ways to shape it: <strong>boot from RAM</strong> when you want a disk-light appliance, reach for <strong>MaaS</strong> or <strong>DGX Spark</strong> when that's where your hardware lives, and use the first <strong>Hadron extension layers</strong> when the base image doesn't have quite what you need. The Hadron hardening baseline and continued confidential-computing work point at the same underlying goal — Kairos as a foundation you can trust on hardware you don't fully control.</p>
<p>You can find the full release notes here: <a href="https://github.com/kairos-io/kairos/releases/tag/v4.2.0" target="_blank" rel="noopener noreferrer" class="">Kairos v4.2.0 on GitHub</a>.</p>
<p>Thanks to everyone who contributed to this release.</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[From Core to Standard: Delivering Kubernetes as a System Extension]]></title>
            <link>https://kairos.io/blog/2026/06/11/core-to-standard-with-system-extensions/</link>
            <guid>https://kairos.io/blog/2026/06/11/core-to-standard-with-system-extensions/</guid>
            <pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[A proof-of-concept that turns an unmodified Kairos core image into a Kubernetes-ready "standard" node at runtime using a system extension, with the trade-offs, and a call for feedback.]]></description>
            <content:encoded><![CDATA[<p>Kairos ships two kinds of images. A "core" image is just the immutable OS. A "standard"
image is that same core with a Kubernetes layer baked in: the k8s provider plugin, edgevpn,
and the k3s or k0s binaries with their service units. Those extra files are added at build
time by kairos-init, and once they are in the image they are part of it for the life of that
release.</p>
<p>That packaging is convenient, but it ties two things together that do not really need to be
tied: the operating system and the Kubernetes distribution running on top of it. I spent some
time on a proof-of-concept that pulls them apart, and I would like to show you what it looks
like and, more importantly, hear whether you think it is worth pursuing.</p>
<p>The repository is here: <a href="https://github.com/jimmykarily/provider-kairos-extension" target="_blank" rel="noopener noreferrer" class="">https://github.com/jimmykarily/provider-kairos-extension</a></p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-idea">The idea<a href="https://kairos.io/blog/2026/06/11/core-to-standard-with-system-extensions/#the-idea" class="hash-link" aria-label="Direct link to The idea" title="Direct link to The idea" translate="no">​</a></h2>
<p>Everything a standard image adds on top of a core image is, in the end, just files on the
root filesystem. So instead of baking those files into the OS at build time, what if we built
them once and shipped them as a system extension that you apply to an unmodified core image at
runtime?</p>
<p>That is the whole proof-of-concept. Take any released systemd-based core image, for example
core Hadron, apply the extension, and it becomes a Kubernetes node. No OS rebuild, no special
image.</p>
<p>One detail worth getting right up front: the extension packages provider-kairos, not only k3s.
provider-kairos is the piece that knows how to bring up and manage a Kubernetes distribution on
a Kairos node. k3s is just the distro it happens to manage here. The k3s binary itself is laid
down by the provider's own build hook, which is the exact mechanism kairos-init already uses
when it builds a standard image. So we are not reimplementing how Kubernetes gets installed. We
are taking the same result and delivering it through a different channel.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-you-use-it">How you use it<a href="https://kairos.io/blog/2026/06/11/core-to-standard-with-system-extensions/#how-you-use-it" class="hash-link" aria-label="Direct link to How you use it" title="Direct link to How you use it" translate="no">​</a></h2>
<p>Activation is a single cloud-config file. There are no manual kairos-agent commands to run and
nothing to remember after the fact. Each release of the extension ships an activation.yaml with
the download URLs already filled in.</p>
<p>On a core node that is already installed and booted, you drop the file in <code>/oem/</code> and reboot:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">curl</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">-fsSL</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">-o</span><span class="token plain"> /oem/90_provider-kairos.yaml </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  https://github.com/jimmykarily/provider-kairos-extension/releases/download/v0.0.1/activation.yaml</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token function" style="color:#d73a49">reboot</span><br></div></code></pre></div></div>
<p>If you would rather have a fresh install come up as a Kubernetes node directly, include the same
contents in your install user-data instead.</p>
<p>The activation config itself is small. For a single-node k3s setup it comes down to this:</p>
<div class="language-yaml codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-yaml codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic">#cloud-config</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">stages</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">network</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain"> </span><span class="token key atrule" style="color:#00a4db">name</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Install the provider-kairos extension (once)"</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token key atrule" style="color:#00a4db">if</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'[ ! -e /var/lib/kairos/extensions/provider-kairos.sysext.raw ]'</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token key atrule" style="color:#00a4db">commands</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain"> kairos</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">agent sysext install https</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain">//github.com/jimmykarily/provider</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">kairos</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">extension/releases/download/v0.0.1/provider</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">kairos.sysext.raw</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain"> </span><span class="token key atrule" style="color:#00a4db">name</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"Enable the extension and link the provider plugin"</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token key atrule" style="color:#00a4db">commands</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain"> kairos</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">agent sysext enable </span><span class="token punctuation" style="color:#393A34">-</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">active </span><span class="token punctuation" style="color:#393A34">-</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">now provider</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">kairos</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain"> mkdir </span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">p /usr/local/system/providers</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain"> ln </span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">sf /usr/local/bin/agent</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">provider</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">kairos /usr/local/system/providers/agent</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">provider</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">kairos</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">k3s</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">enabled</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean important" style="color:#36acaa">true</span><br></div></code></pre></div></div>
<p>The first boot downloads the extension and brings k3s up on the same boot. Later boots already
have it enabled, so immucore merges it during initramfs and the install step is skipped. For a
multi-node cluster you set <code>p2p.network_token</code> instead of the single-node <code>k3s.enabled</code> block.</p>
<p>Once the node is back up you can confirm it worked:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token plain">systemd-sysext status </span><span class="token operator" style="color:#393A34">|</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">grep</span><span class="token plain"> provider-kairos   </span><span class="token comment" style="color:#999988;font-style:italic"># the extension is merged</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">k3s </span><span class="token parameter variable" style="color:#36acaa">--version</span><span class="token plain">                                   </span><span class="token comment" style="color:#999988;font-style:italic"># the binary is there</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">k3s kubectl get nodes                            </span><span class="token comment" style="color:#999988;font-style:italic"># the node should reach Ready shortly</span><br></div></code></pre></div></div>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-you-get-out-of-it">What you get out of it<a href="https://kairos.io/blog/2026/06/11/core-to-standard-with-system-extensions/#what-you-get-out-of-it" class="hash-link" aria-label="Direct link to What you get out of it" title="Direct link to What you get out of it" translate="no">​</a></h2>
<p>The most useful consequence is that the Kubernetes layer stops being tied to the OS release.</p>
<p>For you, that means you can move Kubernetes forward without touching the OS underneath it.
Bumping the k3s or k0s version becomes a matter of upgrading the extension rather than waiting
for a new OS image, rebuilding, and reinstalling. The same core image can be a plain node today
and a Kubernetes node tomorrow, decided at runtime by whether you apply the extension, instead
of being a choice you locked in when you picked which image to download. And on systemd flavors
the extension brings the usual sysext properties with it: it is immutable, and under trusted
boot it is signed and measured, with clean upgrade and rollback.</p>
<p>None of this relies on anything exotic. It is built out of mechanisms Kairos already has:
<code>kairos-agent sysext</code>, cloud-config boot stages, and the provider build hook.</p>
<p>There is a benefit for the project too, even if it is less visible from the outside. Today the
standard-image build jobs sit on the critical path of a Kairos release, so a k3s or k0s CVE, a
flaky download, or a scanner tripping on something outside our control can hold up the entire
release, including the core artifacts that have nothing to do with Kubernetes. Delivering the
Kubernetes layer as its own artifact removes that coupling: the base image ships on its own
cadence, and the Kubernetes layer is published and updated separately. That makes releasing
Kairos itself simpler and less fragile, which in the end is good for everyone relying on those
releases.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-trade-offs">The trade-offs<a href="https://kairos.io/blog/2026/06/11/core-to-standard-with-system-extensions/#the-trade-offs" class="hash-link" aria-label="Direct link to The trade-offs" title="Direct link to The trade-offs" translate="no">​</a></h2>
<p>I want to be straight about the costs, because there is a real one.</p>
<p>The biggest is that upgrades are no longer fully atomic. Today, an upgrade swaps the whole
immutable image in a single transaction, Kubernetes layer included. With this approach the OS
and the Kubernetes layer upgrade independently: you move the OS forward by upgrading the image,
and you move Kubernetes forward by upgrading the extension. That independence is exactly what
buys us the decoupling above, but it is the other side of the same coin.</p>
<p>It is worth being concrete about why that matters, because it goes deeper than "two upgrades
instead of one." A lot of what makes Kairos feel safe to upgrade rests on a simple guarantee: if
something goes wrong, the rollback, whether automatic or a manual boot into the passive image,
will work, because the passive image is exactly the thing that was running and working before.
It is a known-good combination that has already proven itself on this machine.</p>
<p>Once the OS and Kubernetes versions can be mixed and matched, that guarantee gets shakier. You
could end up booting the passive, previously-working OS image alongside a newer Kubernetes
version that was never tried together with it. The fallback you are counting on is suddenly a
combination the node has never actually run. Making this safe again would take some redesign in
the Kairos upgrade flow, so that the combination that was known to work is always preserved and
ready to boot if the new one fails. Kairos does not support that neatly today, precisely because
it was built on the assumption that an upgrade is one atomic thing. If you specifically value
that everything on the node moves together in a single step, with a rollback you can fully trust,
this approach asks you to give that up for now.</p>
<p>There is also a little more machinery at activation time than I would like. The paths where
kairos-agent looks for provider plugins are not among the directories a sysext is allowed to
overlay, so the activation config has to symlink the plugin into <code>/usr/local/system/providers/</code>
itself. It is reliable, because the network stage that does it runs before kairos-agent (the
agent's service is ordered <code>After=cos-setup-network.service</code>), but it is still a step that a
baked-in standard image does not need. As you will see below, this is one of the things that
could simply disappear with a small upstream change.</p>
<p>Finally, this is a proof-of-concept, and it has the rough edges of one. The current builds are
unsigned and amd64 only, and the system-extension path covers systemd flavors first. OpenRC
flavors such as Alpine are not handled by the sysext yet; they would come through a separate
bundle artifact, which is on the list but not done.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-the-poc-stands">Where the PoC stands<a href="https://kairos.io/blog/2026/06/11/core-to-standard-with-system-extensions/#where-the-poc-stands" class="hash-link" aria-label="Direct link to Where the PoC stands" title="Direct link to Where the PoC stands" translate="no">​</a></h2>
<p>The extension builds from start to finish and produces the file you apply to a node. There is
also an automated test that takes a real released core image, applies the extension, and checks
that Kubernetes comes up just like it would on a standard image. That test passes, so the core
idea is proven: you really can take an unmodified core image and turn it into a working
Kubernetes node this way.</p>
<p>Beyond that, the bundle path for OpenRC flavors and the release pipeline are the next pieces of
work.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-would-make-this-genuinely-nice">What would make this genuinely nice<a href="https://kairos.io/blog/2026/06/11/core-to-standard-with-system-extensions/#what-would-make-this-genuinely-nice" class="hash-link" aria-label="Direct link to What would make this genuinely nice" title="Direct link to What would make this genuinely nice" translate="no">​</a></h2>
<p>The proof-of-concept stands on its own, but a couple of small changes upstream in Kairos would
take it from "works, with a few steps" to "barely any steps at all." These are the things I
would want feedback on before going further:</p>
<ul>
<li class="">Let extensions ship the provider binaries. If Kairos looked for provider plugins in a
directory that a sysext is allowed to populate, the extension could carry the plugin directly
and the activation symlink step would go away entirely.</li>
<li class="">Let extensions ship their own cloud-config. With a lookup directory for cloud-config that an
extension can populate, the extension could carry its own activation stage, and the only thing
a user would write is the k3s or p2p block.</li>
<li class="">Reuse the same artifact on Alpine too. On systemd flavors we keep using systemd-sysext, so we
do not give up anything it offers now or later. The gap is that systemd-sysext is not there on
OpenRC flavors like Alpine, so the same <code>.raw</code> does not apply. If immucore did the final overlay
mount itself on those flavors, the same extension file could be reused there as well: the
binaries inside are init-agnostic, and the systemd units are simply ignored. That would let one
artifact cover both worlds instead of building a separate bundle for Alpine.</li>
<li class="">Give it a home in provider-kairos. provider-kairos already owns the build hook, so it is the
natural place to produce and release the extension as part of its own releases.</li>
</ul>
<p>One security note on the first two, since it matters: the new lookup directories would be
root-equivalent sinks, because boot cloud-config runs as root and provider binaries are executed
as root. So they have to be root-owned rather than writable by an unprivileged user. That is not
a new privilege boundary, though. Installing an extension already implies root, and under trusted
boot the extension's contents are signature-verified.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="try-it-and-tell-me-what-you-think">Try it, and tell me what you think<a href="https://kairos.io/blog/2026/06/11/core-to-standard-with-system-extensions/#try-it-and-tell-me-what-you-think" class="hash-link" aria-label="Direct link to Try it, and tell me what you think" title="Direct link to Try it, and tell me what you think" translate="no">​</a></h2>
<p>If any of this sounds useful, the best thing you can do is try it. Grab a release, apply the
activation config to a core image, and see how it feels compared to a standard image. Then come
tell me what broke, what surprised you, and whether the trade-off lands well for your use case.</p>
<p>The real question I am trying to answer is the one in the trade-offs section: is decoupling the
Kubernetes layer from the OS worth giving up fully-atomic upgrades? My own hunch is that for a
lot of people it is, but I would much rather hear it from you than guess.</p>
<p>I have opened <a href="https://github.com/kairos-io/kairos/discussions/4170" target="_blank" rel="noopener noreferrer" class="">a discussion thread</a> to collect feedback in one place,
so please leave your thoughts there rather than scattering them around. You are of course also
welcome in the wider <a href="https://kairos.io/community/" target="_blank" rel="noopener noreferrer" class="">Kairos community</a>. If there is appetite for
the direction, the upstream pieces above are small and well scoped, and they would make this
simpler for everyone who comes after.</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Kairos v4.1.0: From Image Build to Managed Nodes with AuroraBoot]]></title>
            <link>https://kairos.io/blog/2026/05/15/kairos-v4-1-0-hadron-ubuntu-boot-install-foundations/</link>
            <guid>https://kairos.io/blog/2026/05/15/kairos-v4-1-0-hadron-ubuntu-boot-install-foundations/</guid>
            <pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Kairos v4.1.0 tightens the path from image build to managed nodes via kairos-agent phone-home and AuroraBoot v0.20.0’s web UI and fleet server mode, with supporting updates across Hadron, Ubuntu 26.04, boot, install, distros, and release automation.]]></description>
            <content:encoded><![CDATA[<p>Kairos v4.1.0 is now available.</p>
<p>This release improves the path from building a Kairos image to deploying and managing real nodes. <strong><code>kairos-agent</code> now includes phone-home support</strong>, which works together with <strong><a href="https://github.com/kairos-io/AuroraBoot" target="_blank" rel="noopener noreferrer" class="">AuroraBoot</a> v0.20.0</strong> and its web UI when you run it in fleet server mode. Nodes produced through that flow can come online, report back after first boot using phone-home, and show up in AuroraBoot’s node manager.</p>
<p>Behind that story, v4.1.0 also ships <strong>Hadron v0.2.0</strong> for Hadron-based Kairos images, <strong>Ubuntu 26.04</strong> support in <code>kairos-init</code>, boot and install/disk hardening, broader distro compatibility, and release automation improvements. These layers all support the same operational direction: a dependable lifecycle around immutable images.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="from-image-creation-to-managed-nodes">From image creation to managed nodes<a href="https://kairos.io/blog/2026/05/15/kairos-v4-1-0-hadron-ubuntu-boot-install-foundations/#from-image-creation-to-managed-nodes" class="hash-link" aria-label="Direct link to From image creation to managed nodes" title="Direct link to From image creation to managed nodes" translate="no">​</a></h2>
<p>Kairos v4.1.0 adds phone-home support in <code>kairos-agent</code>. On its own, that gives nodes a way to signal back after installation or first boot. <strong>AuroraBoot v0.20.0</strong>, which is a separate project that works alongside Kairos, adds an end-to-end node build and deployment flow through its <strong>web UI</strong>.</p>
<p>AuroraBoot can run as a <strong>self-hosted fleet server</strong>: a single deployment that brings together a <strong>dashboard</strong>, <strong>REST API</strong>, <strong>node manager</strong>, <strong>SecureBoot key store</strong>, and <strong>netboot</strong> server. The web UI walks you through building an artifact, deploying it, and managing nodes after they appear.</p>
<p>Nodes built through AuroraBoot can <strong>phone home automatically on first boot</strong> (via <code>kairos-agent</code>) and land in the <strong>Nodes</strong> list in AuroraBoot. From there, you can drive actions such as upgrade, reboot, reset, applying cloud-config, or running allowed commands.</p>
<p>That combination matters because image-based systems are not only about producing a bootable image. They also need a <strong>reliable operational path</strong> from image creation through installation, first boot, registration, and ongoing lifecycle management. <code>kairos-agent</code> and AuroraBoot address that gap as complementary pieces: Kairos on the node, AuroraBoot in the control plane you choose to run.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="hadron-based-images-now-use-hadron-v020">Hadron-based images now use Hadron v0.2.0<a href="https://kairos.io/blog/2026/05/15/kairos-v4-1-0-hadron-ubuntu-boot-install-foundations/#hadron-based-images-now-use-hadron-v020" class="hash-link" aria-label="Direct link to Hadron-based images now use Hadron v0.2.0" title="Direct link to Hadron-based images now use Hadron v0.2.0" translate="no">​</a></h2>
<p>Hadron-based Kairos images move to <strong>Hadron v0.2.0</strong>, updating the minimal Linux foundation those images are built on. This is an important supporting change for anyone using the official Hadron-based artifacts, but it sits alongside the broader provisioning and lifecycle work above.</p>
<p>Hadron remains the upstream-first base we use for a smaller, more controlled foundation while lifecycle, provisioning, and Kubernetes integration stay in the Kairos layer.</p>
<p>Hadron v0.2.0 includes updates such as:</p>
<ul>
<li class="">Linux kernel updated to <code>7.0.6</code></li>
<li class="">DirtyFrag mitigation by blocklisting the affected <code>nf_defrag_ipv4</code> and <code>nf_defrag_ipv6</code> kernel modules by default</li>
<li class="">Thor GPU image example and documentation</li>
<li class="">Additional ARM64 Nvidia kernel configuration</li>
<li class="">GRUB SMBIOS support</li>
<li class="">Parameterized Dockerfile base image and tag support</li>
<li class="">RISC-V images included in Hadron’s multi-architecture manifests</li>
</ul>
<p><strong>RISC-V caveat:</strong> Hadron v0.2.0 publishes RISC-V in its multi-architecture manifests as groundwork for the ecosystem. <strong>Kairos does not publish RISC-V artifacts yet</strong>, so this is not a user-testable Kairos target today—only preparation for future work.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="ubuntu-2604-support">Ubuntu 26.04 support<a href="https://kairos.io/blog/2026/05/15/kairos-v4-1-0-hadron-ubuntu-boot-install-foundations/#ubuntu-2604-support" class="hash-link" aria-label="Direct link to Ubuntu 26.04 support" title="Direct link to Ubuntu 26.04 support" translate="no">​</a></h2>
<p>For users building Kairos from existing distribution bases, v4.1.0 adds support for <strong>Ubuntu 26.04</strong> in <code>kairos-init</code>.</p>
<p>This continues one of the core Kairos ideas: users should be able to bring their own base image while still getting an image-based, Kubernetes-native lifecycle model on top.</p>
<p>Kairos is not tied to a single Linux distribution. Instead, it provides the tooling and lifecycle model around different bases, whether that is Ubuntu, Fedora, Alpine, openSUSE, Debian, Rocky, or Hadron.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="better-boot-flows">Better boot flows<a href="https://kairos.io/blog/2026/05/15/kairos-v4-1-0-hadron-ubuntu-boot-install-foundations/#better-boot-flows" class="hash-link" aria-label="Direct link to Better boot flows" title="Direct link to Better boot flows" translate="no">​</a></h2>
<p>Kairos v4.1.0 includes several boot-related improvements.</p>
<p><code>immucore</code> now includes TPM kernel module support during UKI boot, and <code>kairos-agent</code> improves <code>systemd-boot</code> support with assessment suffix handling.</p>
<p>These are lower-level changes, but they matter for the direction of the project. Image-based systems are not only about producing a bootable artifact. They also need reliable boot flows, recovery paths, and support for more trusted and measured boot scenarios.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="more-robust-install-and-disk-handling">More robust install and disk handling<a href="https://kairos.io/blog/2026/05/15/kairos-v4-1-0-hadron-ubuntu-boot-install-foundations/#more-robust-install-and-disk-handling" class="hash-link" aria-label="Direct link to More robust install and disk handling" title="Direct link to More robust install and disk handling" translate="no">​</a></h2>
<p>This release also includes a set of practical improvements around installation and disk handling.</p>
<p>Notable changes include:</p>
<ul>
<li class="">support for resolving <code>script://</code> disk paths through the <code>yip</code> helper</li>
<li class="">JSON schema updates for the new <code>script://</code> disk schema</li>
<li class="">flexible disk improvements in <code>yip</code></li>
<li class="">a fix for bytes-vs-sectors mismatch in partition expansion</li>
<li class="">support for handling more than only NVMe devices</li>
<li class="">loopback detach fixes during install flows</li>
</ul>
<p>These are the kinds of changes that are easy to miss in a changelog but important in real deployments. Installation reliability depends on a long tail of hardware, disk layouts, bootloaders, and provisioning paths. v4.1.0 improves several of those edges.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="broader-distro-compatibility">Broader distro compatibility<a href="https://kairos.io/blog/2026/05/15/kairos-v4-1-0-hadron-ubuntu-boot-install-foundations/#broader-distro-compatibility" class="hash-link" aria-label="Direct link to Broader distro compatibility" title="Direct link to Broader distro compatibility" translate="no">​</a></h2>
<p>Kairos v4.1.0 also improves compatibility across different Linux bases.</p>
<p>This includes:</p>
<ul>
<li class="">adjusted network module detection for RHEL 9.0</li>
<li class="">Oracle Linux detection as part of the RHEL-family matching logic</li>
<li class="">a more resilient RHEL install flow that tries the <code>epel-release</code> package first and falls back to a URL</li>
<li class="">machine-id generation fixes for OpenRC systems in recovery mode</li>
</ul>
<p>This is part of the ongoing work to keep Kairos usable across different base distributions and operating environments.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="release-and-automation-improvements">Release and automation improvements<a href="https://kairos.io/blog/2026/05/15/kairos-v4-1-0-hadron-ubuntu-boot-install-foundations/#release-and-automation-improvements" class="hash-link" aria-label="Direct link to Release and automation improvements" title="Direct link to Release and automation improvements" translate="no">​</a></h2>
<p>Kairos v4.1.0 also improves the release process itself.</p>
<p>The release includes:</p>
<ul>
<li class="">automated release notes diff changes</li>
<li class="">idempotent GCP upload script behavior</li>
<li class="">better import task timeout handling and error output</li>
<li class="">non-blocking release behavior for k0s/k3s</li>
<li class="">GitHub Actions updates</li>
<li class="">least-privilege GitHub Actions workflow hardening</li>
</ul>
<p>This kind of work is not always visible to end users, but it improves the reliability and maintainability of the project.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="looking-ahead">Looking ahead<a href="https://kairos.io/blog/2026/05/15/kairos-v4-1-0-hadron-ubuntu-boot-install-foundations/#looking-ahead" class="hash-link" aria-label="Direct link to Looking ahead" title="Direct link to Looking ahead" translate="no">​</a></h2>
<p>Kairos v4.1.0 puts a <strong>clearer path from building images to deploying and managing nodes</strong> at the center of the story. <strong><code>kairos-agent</code> phone-home support</strong> and <strong>AuroraBoot v0.20.0’s web UI and fleet server mode</strong> are the most visible parts of that arc.</p>
<p><strong>Hadron v0.2.0</strong>, <strong>Ubuntu 26.04</strong> support in <code>kairos-init</code>, boot improvements, disk and install fixes, distro compatibility, and release automation all push in the same direction: an image-based OS is <strong>not only an image</strong>. It is the <strong>lifecycle</strong> around that image—<strong>build</strong>, <strong>install</strong>, <strong>boot</strong>, <strong>register</strong>, <strong>upgrade</strong>, <strong>recover</strong>, and <strong>operate</strong>—and v4.1.0 advances each of those layers.</p>
<p>You can find the full release notes here: <a href="https://github.com/kairos-io/kairos/releases/tag/v4.1.0" target="_blank" rel="noopener noreferrer" class="">Kairos v4.1.0 on GitHub</a>.</p>
<p>Thanks to everyone who contributed to this release.</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Help Kairos Move to CNCF Incubation: Become an Adopter]]></title>
            <link>https://kairos.io/blog/2026/04/09/become-a-kairos-adopter-for-cncf-incubation/</link>
            <guid>https://kairos.io/blog/2026/04/09/become-a-kairos-adopter-for-cncf-incubation/</guid>
            <pubDate>Thu, 09 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Kairos community,]]></description>
            <content:encoded><![CDATA[<p>Kairos community,</p>
<p>We are preparing the next major step in our CNCF journey: applying to move from Sandbox to <strong>Incubation</strong>.</p>
<p>To do that, we need to demonstrate healthy and diverse real-world adoption. As part of the <a href="https://github.com/cncf/toc/blob/main/process/README.md" target="_blank" rel="noopener noreferrer" class="">official CNCF TOC project lifecycle and process</a>, projects are expected to provide <strong>5-7 adopters</strong> willing to be interviewed during due diligence.</p>
<p>Today, we are inviting organizations using Kairos to participate as adopters and help us through this milestone.</p>
<p>We also understand adoption takes time. If you are currently in a proof-of-concept stage, that is absolutely okay. We would still love to talk, learn from your experience, and help you move toward pre-production and production in any way we can.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-incubation">Why Incubation?<a href="https://kairos.io/blog/2026/04/09/become-a-kairos-adopter-for-cncf-incubation/#why-incubation" class="hash-link" aria-label="Direct link to Why Incubation?" title="Direct link to Why Incubation?" translate="no">​</a></h2>
<p>Incubation is where CNCF projects start demonstrating stronger maturity signals: more stability, broader production usage, and clearer evidence that the project is useful in real environments.</p>
<p>For Kairos, this helps us:</p>
<ul>
<li class="">Strengthen long-term credibility in the cloud-native ecosystem</li>
<li class="">Validate production readiness through independent adopter feedback</li>
<li class="">Accelerate project growth while keeping development open and vendor-neutral</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-signal-that-kairos-is-growing-in-the-open">A signal that Kairos is growing in the open<a href="https://kairos.io/blog/2026/04/09/become-a-kairos-adopter-for-cncf-incubation/#a-signal-that-kairos-is-growing-in-the-open" class="hash-link" aria-label="Direct link to A signal that Kairos is growing in the open" title="Direct link to A signal that Kairos is growing in the open" translate="no">​</a></h2>
<p>This effort is part of a broader direction for Kairos.</p>
<p>We recently welcomed our first maintainer from a different company than the original Kairos creators, a concrete sign of growing shared ownership and open governance:</p>
<ul>
<li class=""><a href="https://kairos.io/blog/2026/01/15/welcome-william-rizzo-new-kairos-maintainer/" target="_blank" rel="noopener noreferrer" class="">Welcome William Rizzo, New Kairos Maintainer</a></li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-it-means-to-be-a-kairos-adopter">What it means to be a Kairos adopter<a href="https://kairos.io/blog/2026/04/09/become-a-kairos-adopter-for-cncf-incubation/#what-it-means-to-be-a-kairos-adopter" class="hash-link" aria-label="Direct link to What it means to be a Kairos adopter" title="Direct link to What it means to be a Kairos adopter" translate="no">​</a></h2>
<p>Being an adopter means your organization uses Kairos in a meaningful way (proof of concept, pilot, pre-production, or production) and can share practical feedback, including:</p>
<ul>
<li class="">Why you chose Kairos</li>
<li class="">Which use cases you support with it</li>
<li class="">What value it brings in operations, reliability, security, or scale</li>
<li class="">What challenges you faced and how we can improve</li>
</ul>
<p>You do not need to be a large enterprise, and you do not need to be a direct code contributor.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-cncf-may-ask-from-your-organization">What CNCF may ask from your organization<a href="https://kairos.io/blog/2026/04/09/become-a-kairos-adopter-for-cncf-incubation/#what-cncf-may-ask-from-your-organization" class="hash-link" aria-label="Direct link to What CNCF may ask from your organization" title="Direct link to What CNCF may ask from your organization" translate="no">​</a></h2>
<p>If selected as one of the adopter references, your organization may be contacted by CNCF TOC sponsors for an adopter interview as part of the incubation due diligence process.</p>
<p>These interviews typically cover:</p>
<ul>
<li class="">Adoption context and timeline</li>
<li class="">Current usage stage and scale</li>
<li class="">Perception of project maturity and governance</li>
<li class="">Strengths, gaps, and future needs</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="confidentiality-and-publication-boundaries">Confidentiality and publication boundaries<a href="https://kairos.io/blog/2026/04/09/become-a-kairos-adopter-for-cncf-incubation/#confidentiality-and-publication-boundaries" class="hash-link" aria-label="Direct link to Confidentiality and publication boundaries" title="Direct link to Confidentiality and publication boundaries" translate="no">​</a></h3>
<p>We understand many teams have legal or commercial constraints.</p>
<p>The CNCF process can accommodate adopter anonymity and publication boundaries when needed, and adopter interview summaries are reviewed with adopters before publication.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-your-organization-gets">What your organization gets<a href="https://kairos.io/blog/2026/04/09/become-a-kairos-adopter-for-cncf-incubation/#what-your-organization-gets" class="hash-link" aria-label="Direct link to What your organization gets" title="Direct link to What your organization gets" translate="no">​</a></h2>
<p>We see this as a practical collaboration where both sides benefit.</p>
<p>By participating, your organization can:</p>
<ul>
<li class="">Support a CNCF Sandbox project advancing toward Incubation</li>
<li class="">Be recognized in CNCF-related due diligence materials when disclosure is allowed</li>
<li class="">Stay close to the Kairos roadmap and maintainer discussions</li>
<li class="">Share engineering feedback that directly influences project priorities</li>
</ul>
<p>And if your organization wants public recognition, we can also:</p>
<ul>
<li class="">Feature your organization as a Kairos adopter on the Kairos website</li>
<li class="">Include your logo on our adopters page (fully opt-in, based on your approval and brand guidelines)</li>
<li class="">Collaborate on public technical stories, including potential CNCF blog posts</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="interested-in-joining-as-an-adopter">Interested in joining as an adopter?<a href="https://kairos.io/blog/2026/04/09/become-a-kairos-adopter-for-cncf-incubation/#interested-in-joining-as-an-adopter" class="hash-link" aria-label="Direct link to Interested in joining as an adopter?" title="Direct link to Interested in joining as an adopter?" translate="no">​</a></h2>
<p>If your organization is using Kairos and is open to this conversation, you can:</p>
<ul>
<li class="">Apply publicly through our adopter application issue template: <a href="https://github.com/kairos-io/kairos/issues/new?template=adopter-application.yml" target="_blank" rel="noopener noreferrer" class="">Become a Kairos adopter</a></li>
<li class="">Reach out privately by email at <a href="mailto:members@kairos.io" target="_blank" rel="noopener noreferrer" class="">members@kairos.io</a></li>
</ul>
<p>When you contact us, it helps if you include:</p>
<ul>
<li class="">Organization name</li>
<li class="">Main use case</li>
<li class="">Current stage (pilot, pre-production, or production)</li>
<li class="">Preferred visibility level (public, limited public, or private first)</li>
</ul>
<p>Thanks for helping us take Kairos to the next level.</p>
<p>This milestone is about more than project status. It is about proving, together, that Kairos is delivering real value in real systems.</p>]]></content:encoded>
            <category>Kairos</category>
            <category>CNCF</category>
        </item>
        <item>
            <title><![CDATA[Kairos release v4.0.0]]></title>
            <link>https://kairos.io/blog/2026/02/27/kairos-release-v4.0.0/</link>
            <guid>https://kairos.io/blog/2026/02/27/kairos-release-v4.0.0/</guid>
            <pubDate>Fri, 27 Feb 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Why Kairos v4 changes artifact publication while preserving distro choice.]]></description>
            <content:encoded><![CDATA[<p>Kairos v4.0.0 is the result of a clear architecture path we have been building over time: first standardizing image creation with <code>kairos-init</code>, then making that flow easy to run anywhere with <a class="" href="https://kairos.io/docs/reference/kairos-factory/">Kairos Factory</a> and <a href="https://github.com/kairos-io/kairos-factory-action" target="_blank" rel="noopener noreferrer" class=""><code>kairos-factory-action</code></a>, and finally introducing <a class="" href="https://kairos.io/blog/2025/12/17/introducing-hadron-the-minimal-upstream-first-linux-base-for-kairos/">Hadron</a>.</p>
<p>In March 2025, we introduced <a class="" href="https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/"><code>kairos-init</code></a>, a foundational shift that removed Dockerfile-heavy distro logic and standardized how we transform OCI bases into Kairos images.</p>
<p>From there, we focused on operationalizing that model so anyone could run it. With <a class="" href="https://kairos.io/docs/reference/kairos-factory/">Kairos Factory</a>, users can build and maintain their own Kairos pipelines using the same tooling we run in production.</p>
<p>In December 2025, we introduced <a class="" href="https://kairos.io/blog/2025/12/17/introducing-hadron-the-minimal-upstream-first-linux-base-for-kairos/">Hadron</a>, our upstream-first Linux base for immutable systems. In v4, Hadron artifacts are what the project publishes in its release flow.</p>
<p>At the same time, distro flexibility remains core to Kairos. This is visible in active community work such as Oracle Linux support in <a href="https://github.com/kairos-io/kairos/issues/3987" target="_blank" rel="noopener noreferrer" class="">kairos-io/kairos#3987</a>.</p>
<p>For additional migration and build context, read <a class="" href="https://kairos.io/blog/2026/02/25/kairos-v4-hadron-artifacts-and-distro-flexibility/">Hadron-Only Artifacts with Ongoing Distro Support</a>.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-v4-delivers-in-practice">What v4 delivers in practice<a href="https://kairos.io/blog/2026/02/27/kairos-release-v4.0.0/#what-v4-delivers-in-practice" class="hash-link" aria-label="Direct link to What v4 delivers in practice" title="Direct link to What v4 delivers in practice" translate="no">​</a></h2>
<p>The key technical reassurance in v4 is compatibility in the build pipeline. Between <code>v3.7.2</code> and <code>v4.0.0</code>, the <code>kairos-init</code> version did not change.</p>
<p>This matters because <code>kairos-init</code> is where the core Kairos transformation components are pinned. When that set of components is unchanged, build behavior remains compatible in practice across releases. In practical terms, if your non-Hadron flavor pipeline built successfully with <code>v3.7.2</code>, it should continue to build with <code>v4.0.0</code> under the same assumptions.</p>
<p>For the complete technical details of <code>v4.0.0</code>, see the release notes: <a href="https://github.com/kairos-io/kairos/releases/tag/v4.0.0" target="_blank" rel="noopener noreferrer" class="">kairos v4.0.0</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-to-switch-to-v4">How to switch to v4<a href="https://kairos.io/blog/2026/02/27/kairos-release-v4.0.0/#how-to-switch-to-v4" class="hash-link" aria-label="Direct link to How to switch to v4" title="Direct link to How to switch to v4" translate="no">​</a></h2>
<p>There are two official paths to adopt Kairos v4, and the right one depends on your environment and goals.</p>
<p>One path is to use <a href="https://quay.io/repository/kairos/hadron" target="_blank" rel="noopener noreferrer" class="">Hadron-based images</a>, which are now published as part of the project release flow.</p>
<p>The other path is to keep your current distro flavor and build your own v4 release pipeline. With <a class="" href="https://kairos.io/docs/reference/kairos-factory/">Kairos Factory</a>, you can build and publish your flavor using the same production tooling model we use ourselves.</p>
<p>For migration guidance and build details, read: <a class="" href="https://kairos.io/blog/2026/02/25/kairos-v4-hadron-artifacts-and-distro-flexibility/">Hadron-Only Artifacts with Ongoing Distro Support</a>.</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Hadron-Only Artifacts with Ongoing Distro Support]]></title>
            <link>https://kairos.io/blog/2026/02/25/kairos-v4-hadron-artifacts-and-distro-flexibility/</link>
            <guid>https://kairos.io/blog/2026/02/25/kairos-v4-hadron-artifacts-and-distro-flexibility/</guid>
            <pubDate>Wed, 25 Feb 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Starting with Kairos v4, the project will publish Hadron-based artifacts only.]]></description>
            <content:encoded><![CDATA[<p>Starting with <strong>Kairos v4</strong>, the Kairos project will publish <strong>Hadron-based artifacts only</strong>.</p>
<p>This decision allows us to reduce maintenance costs, focus engineering effort where it has the most impact, and ship improvements faster.</p>
<p>More context in the original issue: <a href="https://github.com/kairos-io/kairos/issues/3806" target="_blank" rel="noopener noreferrer" class="">#3806</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-is-changing">What is changing<a href="https://kairos.io/blog/2026/02/25/kairos-v4-hadron-artifacts-and-distro-flexibility/#what-is-changing" class="hash-link" aria-label="Direct link to What is changing" title="Direct link to What is changing" translate="no">​</a></h2>
<p>Official artifacts published by the Kairos project for v4 and later will be based on Hadron.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-is-not-changing">What is not changing<a href="https://kairos.io/blog/2026/02/25/kairos-v4-hadron-artifacts-and-distro-flexibility/#what-is-not-changing" class="hash-link" aria-label="Direct link to What is not changing" title="Direct link to What is not changing" translate="no">​</a></h2>
<p>Support for different Linux distributions remains one of the core features of Kairos.</p>
<p>The <code>kairos-init</code> component, which is responsible for converting those distributions into Kairos variants, continues to validate a wide distro matrix: <strong>8 different distros and multiple releases</strong>.</p>
<p>You can see the exact test matrix here: <a href="https://github.com/kairos-io/kairos-init/blob/main/.github/workflows/test.yml#L22-L39" target="_blank" rel="noopener noreferrer" class=""><code>kairos-init</code> distro test matrix</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="build-your-own-distro-pipeline">Build your own distro pipeline<a href="https://kairos.io/blog/2026/02/25/kairos-v4-hadron-artifacts-and-distro-flexibility/#build-your-own-distro-pipeline" class="hash-link" aria-label="Direct link to Build your own distro pipeline" title="Direct link to Build your own distro pipeline" translate="no">​</a></h2>
<p>If you are using GitHub, building your own release pipeline for a specific distribution is straightforward with <a href="https://github.com/kairos-io/kairos-factory-action" target="_blank" rel="noopener noreferrer" class=""><code>kairos-factory-action</code></a>.</p>
<p>It is mostly a matter of setting a few parameters, and it is exactly how we still build one-distro pipelines today: <a href="https://github.com/kairos-io/kairos/blob/3ba6e3e9d9d15aa9d3ba0a414d2e512db44f24d7/.github/workflows/release.yaml#L11" target="_blank" rel="noopener noreferrer" class="">Kairos release workflow example</a>.</p>
<p>If you are not using GitHub, no problem: you can build directly with AuroraBoot: <a href="https://kairos.io/docs/reference/auroraboot/" target="_blank" rel="noopener noreferrer" class="">AuroraBoot reference docs</a>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-we-believe-this-is-the-right-move">Why we believe this is the right move<a href="https://kairos.io/blog/2026/02/25/kairos-v4-hadron-artifacts-and-distro-flexibility/#why-we-believe-this-is-the-right-move" class="hash-link" aria-label="Direct link to Why we believe this is the right move" title="Direct link to Why we believe this is the right move" translate="no">​</a></h2>
<p>We understand this may introduce some inconvenience for users who currently rely on project-published artifacts for multiple distros.</p>
<p>At the same time, this change helps us keep Kairos sustainable and gives us more time to focus on features, quality, and platform evolution.</p>
<p>From our side, the overall release matrix grew beyond what we could reliably sustain. Managing multiple distributions across provider variants and Kubernetes combinations (k0s and k3s, each with multiple versions) pushed us to more than 500 artifacts per release cycle.</p>
<p>At that scale, keeping pipelines, CI, and verification checks consistently healthy became increasingly difficult, and the risk of missing artifact signatures or specific version outputs was no longer acceptable.</p>
<p>It also aligns with the Kairos ethos: giving end users control over their own release cadence and distribution flexibility. We do not want users to be blocked by our release timing when their priorities are different. If a critical CVE appears in a component that matters to your environment, you should be able to rebuild and release on your own schedule instead of waiting for our next release window.</p>
<p>Just as importantly, different teams need different upgrade policies. Some users may want kernel or base OS patch updates without moving to a newer k3s version. Others may want to avoid agent bumps and only roll selected OS fixes. This shift is about making that level of control practical, so each team can decide what to update, when to update it, and how fast to promote it through their own pipeline.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="feedback-and-support">Feedback and support<a href="https://kairos.io/blog/2026/02/25/kairos-v4-hadron-artifacts-and-distro-flexibility/#feedback-and-support" class="hash-link" aria-label="Direct link to Feedback and support" title="Direct link to Feedback and support" translate="no">​</a></h2>
<p>If you have questions, issues, or feedback, please reach out:</p>
<p>Open an issue on GitHub: <a href="https://github.com/kairos-io/kairos/issues/new/choose" target="_blank" rel="noopener noreferrer" class="">https://github.com/kairos-io/kairos/issues/new/choose</a>.</p>
<p>Join the CNCF Slack (<code>#kairos</code>): <a href="https://slack.cncf.io/" target="_blank" rel="noopener noreferrer" class="">https://slack.cncf.io/</a>.</p>
<p>If you or your team plan to publicly build and distribute Kairos for a specific distro, please let us know. We would love to coordinate and help identify the best way to promote you.</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Welcome William Rizzo, New Kairos Maintainer]]></title>
            <link>https://kairos.io/blog/2026/01/15/welcome-william-rizzo-new-kairos-maintainer/</link>
            <guid>https://kairos.io/blog/2026/01/15/welcome-william-rizzo-new-kairos-maintainer/</guid>
            <pubDate>Thu, 15 Jan 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[We are happy to welcome William Rizzo as a new Kairos maintainer.]]></description>
            <content:encoded><![CDATA[<p>We are happy to welcome William Rizzo as a new Kairos maintainer.</p>
<p>William is a CNCF Ambassador and Linkerd Ambassador, and he currently works at Mirantis as a Global Field CTO. He helps organizations design, build, and run platforms across edge, AI, and platform engineering. His background spans engineering, product ownership, pre- and post-sales, and consulting, with experience in HPC, storage, and large-scale distributed systems.</p>
<p>Open source and cloud-native communities are a major part of William's professional identity. He actively volunteers in several Cloud Native groups and helps organize KCD Netherlands. He also brings public speaking experience from community talks. He is a strong addition to the team, bringing years of experience in the field and a collaborative, community-first approach.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-milestone-for-the-project">A milestone for the project<a href="https://kairos.io/blog/2026/01/15/welcome-william-rizzo-new-kairos-maintainer/#a-milestone-for-the-project" class="hash-link" aria-label="Direct link to A milestone for the project" title="Direct link to A milestone for the project" translate="no">​</a></h2>
<p>William is the first Kairos maintainer from a different company than the original Kairos creators, and that is a meaningful signal for the ecosystem. It shows the value Kairos brings beyond its origins and highlights growing, shared ownership of the project.</p>
<p>This kind of external maintainer support is also one of the prerequisites for applying for CNCF Incubation, and it aligns with our commitment to keep building Kairos in the open.</p>
<p>As Kairos continues to grow and bring in external maintainers, we realized this was the right moment to strengthen and formalize our governance. We have introduced an auditable voting process using GitVote so that maintainer decisions are publicly recorded in GitHub. As part of this transition, the Kairos maintainers have formally ratified William's maintainer status under the new governance model through a recorded GitVote in <a href="https://github.com/kairos-io/kairos/issues/3855" target="_blank" rel="noopener noreferrer" class="">issue #3855</a>. This vote does not change William's role; it documents it in a way that is accountable and meaningful for both him and the community.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-william-joined">Why William joined<a href="https://kairos.io/blog/2026/01/15/welcome-william-rizzo-new-kairos-maintainer/#why-william-joined" class="hash-link" aria-label="Direct link to Why William joined" title="Direct link to Why William joined" translate="no">​</a></h2>
<p>William has been contributing to Kairos for some time and is especially excited by how immutability is foundational to the project. As a maintainer, he wants to help Kairos grow both technically and in visibility, so more organizations can adopt the platform successfully.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="focus-areas">Focus areas<a href="https://kairos.io/blog/2026/01/15/welcome-william-rizzo-new-kairos-maintainer/#focus-areas" class="hash-link" aria-label="Direct link to Focus areas" title="Direct link to Focus areas" translate="no">​</a></h2>
<p>William plans to start by owning <code>kairos-capi</code> and expand as he ramps up. His focus is Kubernetes integration and helping Kairos work effectively with it, while other areas remain with the existing maintainers.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="community-talks-and-writing">Community talks and writing<a href="https://kairos.io/blog/2026/01/15/welcome-william-rizzo-new-kairos-maintainer/#community-talks-and-writing" class="hash-link" aria-label="Direct link to Community talks and writing" title="Direct link to Community talks and writing" translate="no">​</a></h2>
<p>Here are a couple of examples of how William promotes Kairos. There are more, and some are variations of the same talk at different events.</p>
<ul>
<li class="">Talk (KubeCon Atlanta 2025, Kubernetes on Edge): <a href="https://www.youtube.com/watch?v=mICAoVlkaIs" target="_blank" rel="noopener noreferrer" class="">The Immutable Lightness of an Edge Platform</a></li>
<li class="">CNCF blog (2025): <a href="https://www.cncf.io/blog/2025/03/25/building-secure-kubernetes-edge-images-with-kairos-and-k0s/" target="_blank" rel="noopener noreferrer" class="">Building Secure Kubernetes Edge Images with Kairos and k0s</a></li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-to-connect">How to connect<a href="https://kairos.io/blog/2026/01/15/welcome-william-rizzo-new-kairos-maintainer/#how-to-connect" class="hash-link" aria-label="Direct link to How to connect" title="Direct link to How to connect" translate="no">​</a></h2>
<ul>
<li class="">GitHub: <a href="https://github.com/wrkode" target="_blank" rel="noopener noreferrer" class="">@wrkode</a></li>
<li class="">Time zone: Europe/Amsterdam</li>
<li class="">CNCF Slack: Will-I-Am</li>
</ul>
<p>Please join us in welcoming William to the maintainer team as we continue to grow Kairos in the open.</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Introducing Hadron: The Minimal, Upstream-First Linux Base for Kairos]]></title>
            <link>https://kairos.io/blog/2025/12/17/introducing-hadron-the-minimal-upstream-first-linux-base-for-kairos/</link>
            <guid>https://kairos.io/blog/2025/12/17/introducing-hadron-the-minimal-upstream-first-linux-base-for-kairos/</guid>
            <pubDate>Wed, 17 Dec 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[The cloud-native and edge-computing world demands systems that are small, reliable, and predictable. For years, the Kairos project has empowered users to turn mainstream Linux distributions, such as Ubuntu, Alpine, Debian, Fedora and more, into immutable, image-based operating systems with secure, atomic A/B updates.]]></description>
            <content:encoded><![CDATA[<p>The cloud-native and edge-computing world demands systems that are small, reliable, and predictable. For years, the Kairos project has empowered users to turn mainstream Linux distributions, such as Ubuntu, Alpine, Debian, Fedora and more, into immutable, image-based operating systems with secure, atomic A/B updates.</p>
<p>That mission remains core to us. But in transforming traditional distributions, we continually encountered friction: the inherited bloat of legacy package managers, sprawling dependency graphs, and downstream patches that increase image size and boot time.</p>
<p>Today, we are excited to announce a new option for the Kairos ecosystem: <a href="https://hadron-linux.io/" target="_blank" rel="noopener noreferrer" class="">Hadron Linux</a>.</p>
<p>Hadron is a brand-new, minimal, and trustworthy Linux distribution engineered from scratch by the Kairos team to be the perfect base for immutable, image-based systems.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-hadron-the-pursuit-of-minimal-predictability">Why Hadron? The Pursuit of Minimal Predictability<a href="https://kairos.io/blog/2025/12/17/introducing-hadron-the-minimal-upstream-first-linux-base-for-kairos/#why-hadron-the-pursuit-of-minimal-predictability" class="hash-link" aria-label="Direct link to Why Hadron? The Pursuit of Minimal Predictability" title="Direct link to Why Hadron? The Pursuit of Minimal Predictability" translate="no">​</a></h2>
<p>Hadron is not "yet another distro". It is a surgical response to the specific needs of cloud-native and edge deployments, and a modern first system, built on the core goals of <strong>ultimate minimalism</strong>, <strong>upstream alignment</strong>, and <strong>reproducibility</strong>.</p>
<table><thead><tr><th>Feature</th><th>Hadron's Approach</th><th>Benefit for Cloud/Edge</th></tr></thead><tbody><tr><td>Base</td><td>Built from scratch, non-derived</td><td>Zero legacy bloat or dependencies</td></tr><tr><td>Components</td><td>Vanilla (musl libc, systemd, unpatched kernel)</td><td>Upstream alignment, minimal drift</td></tr><tr><td>Upgrade Model</td><td>Image-based (via Kairos)</td><td>Atomic A/B updates, safe rollbacks</td></tr><tr><td>Footprint</td><td>Extremely minimal</td><td>Fast boot times, smaller images</td></tr><tr><td>Package Management</td><td>None by design</td><td>No vendor lock-in, use your preferred extension method</td></tr></tbody></table>
<p>This "minimal-first" approach directly translates into reduced attack surface and enhanced security, as fewer components mean fewer vectors for compromise. Hadron is not positioned as a replacement or competitor to established general-purpose distributions like Ubuntu, Debian, or Alpine. Instead, it is an alternative base layer specifically optimized for the constraints and requirements of modern immutable, image-based, cloud-native, and edge systems.</p>
<p>While Kairos continues to support all major distributions, Hadron exists to serve the users who need the absolute smallest footprint, fastest boot times, and most predictable upstream-aligned behavior possible when deploying at scale or in resource-constrained environments. It is a purpose-built tool for a specialized job, complementing, rather than challenging, the broader Linux ecosystem.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-novel-combination-musl--systemd">A Novel Combination: musl + systemd<a href="https://kairos.io/blog/2025/12/17/introducing-hadron-the-minimal-upstream-first-linux-base-for-kairos/#a-novel-combination-musl--systemd" class="hash-link" aria-label="Direct link to A Novel Combination: musl + systemd" title="Direct link to A Novel Combination: musl + systemd" translate="no">​</a></h2>
<p>Hadron is one of the only distributions intentionally combining the <a href="https://www.musl-libc.org/" target="_blank" rel="noopener noreferrer" class="">musl C library</a> with the <a href="https://systemd.io/" target="_blank" rel="noopener noreferrer" class="">systemd init system</a>. This combination is powerful for modern systems:</p>
<ul>
<li class=""><strong>musl</strong>: Provides a small, secure, and reproducible foundation, ideal for cloud-native container workloads.</li>
<li class=""><strong>systemd</strong>: Offers predictable boot, rich observability, and broad ecosystem support through standard APIs.</li>
</ul>
<p>The result is a small footprint, fast boot, while still operating modern operating system needs and consistent behavior across diverse environments, without the complexity of the traditional glibc-based stack.</p>
<table><thead><tr><th>Feature</th><th>Hadron</th><th>Alpine</th><th>Ubuntu</th><th>Red Hat families</th><th>SUSE families</th></tr></thead><tbody><tr><td>Package manager</td><td>None by design</td><td>APK</td><td>apt</td><td>dnf</td><td>zypper</td></tr><tr><td>Libc</td><td>musl</td><td>musl</td><td>glibc</td><td>glibc</td><td>glibc</td></tr><tr><td>Init system</td><td>systemd</td><td>openRC</td><td>systemd</td><td>systemd</td><td>systemd</td></tr><tr><td>Footprint</td><td>Extremely minimal</td><td>Fast boot times, smaller images</td><td>small-medium</td><td>small-medium</td><td>small-medium</td></tr><tr><td>Lifecycle management</td><td>Kairos</td><td>APK</td><td>apt, Snap</td><td>Dnf, bootc, rpm-ostree</td><td>Zypper, Elemental</td></tr></tbody></table>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="hadron-and-kairos-the-perfect-immutable-stack">Hadron and Kairos: The Perfect Immutable Stack<a href="https://kairos.io/blog/2025/12/17/introducing-hadron-the-minimal-upstream-first-linux-base-for-kairos/#hadron-and-kairos-the-perfect-immutable-stack" class="hash-link" aria-label="Direct link to Hadron and Kairos: The Perfect Immutable Stack" title="Direct link to Hadron and Kairos: The Perfect Immutable Stack" translate="no">​</a></h2>
<p>It is critical to understand the relationship:</p>
<p><strong>Kairos</strong> is the project that delivers the immutable, image-based lifecycle, atomic A/B upgrades, and zero-touch provisioning. Kairos remains distro-agnostic and will continue to support all current flavors (Ubuntu, Debian, Fedora, etc.).</p>
<p><strong>Hadron</strong> is the purpose-built, optimal flavor for Kairos, a clean, lean, and predictable base OS.</p>
<p>If you are looking for the smallest, cleanest, most upstream-aligned OS for your cloud-native or edge infrastructure, Hadron is designed for you. You can build your image, extend it using container technologies, or simply use system extensions without ever touching a package manager.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="our-invitation-to-the-community">Our Invitation to the Community<a href="https://kairos.io/blog/2025/12/17/introducing-hadron-the-minimal-upstream-first-linux-base-for-kairos/#our-invitation-to-the-community" class="hash-link" aria-label="Direct link to Our Invitation to the Community" title="Direct link to Our Invitation to the Community" translate="no">​</a></h2>
<p>Hadron is mature and production-ready for its core purpose: to be a minimal, predictable base for Kairos. As part of the CNCF project Kairos, Hadron guarantees vendor neutrality and a clear governance model.</p>
<p>Hadron expands the Kairos matrix with a specialized flavor that will become the new default. All existing flavors remain fully supported, and our commitment to a vendor-neutral, lock-in-free ecosystem stays unchanged—giving you the freedom to choose the base OS that best fits your needs.</p>
<p>We invite you to explore Hadron, try the quickstart guide, and join the conversation:</p>
<ul>
<li class=""><strong>View the Code</strong>: The <a href="https://github.com/kairos-io/hadron" target="_blank" rel="noopener noreferrer" class="">Hadron repository</a> is public on GitHub.</li>
<li class=""><strong>Get Started</strong>: Check out the Hadron documentation <a href="https://kairos.io/quickstart/" target="_blank" rel="noopener noreferrer" class="">quickstart</a>.</li>
<li class=""><strong>Join the Discussion</strong>: Connect with the Kairos and Hadron community on the <a href="https://slack.cncf.io/#kairos" target="_blank" rel="noopener noreferrer" class="">CNCF Slack channel</a>.</li>
</ul>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Growing Stronger: Introducing Commercial Support for Kairos]]></title>
            <link>https://kairos.io/blog/2025/08/08/growing-stronger-introducing-commercial-support-for-kairos/</link>
            <guid>https://kairos.io/blog/2025/08/08/growing-stronger-introducing-commercial-support-for-kairos/</guid>
            <pubDate>Fri, 08 Aug 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Kairos has always been more than just a Linux distro—it's a bold idea: bring the power and flexibility of Kubernetes to the edge, with a truly immutable, secure, and cloud-native operating system anyone can use, contribute to, and trust.]]></description>
            <content:encoded><![CDATA[<p>Kairos has always been more than just a Linux distro—it's a bold idea: bring the power and flexibility of Kubernetes to the edge, with a truly immutable, secure, and cloud-native operating system anyone can use, contribute to, and trust.</p>
<p>Over the past few years, we've seen Kairos go from idea to implementation, and from experimentation to production. Today, it's running in large-scale, real-world deployments across diverse edge use cases. But more importantly—it's been growing as a community.</p>
<p>Today, we're excited to share a new milestone in that journey:<br>
<!-- -->👉 <strong>Kairos now has official commercial support options</strong> available from <a href="https://www.spectrocloud.com/solutions/kairos-support" target="_blank" rel="noopener noreferrer" class="">Spectro Cloud</a>.</p>
<p>Before we dive into what that means, let's take a step back and talk about what makes an open-source project <em>reliable</em>—especially when the stakes are high.</p>
<!-- -->
<hr>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-makes-open-source-reliable">What Makes Open Source Reliable?<a href="https://kairos.io/blog/2025/08/08/growing-stronger-introducing-commercial-support-for-kairos/#what-makes-open-source-reliable" class="hash-link" aria-label="Direct link to What Makes Open Source Reliable?" title="Direct link to What Makes Open Source Reliable?" translate="no">​</a></h2>
<p>In our view, there are two key ingredients that help teams adopt open source with confidence:</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="1-good-governance">1. <strong>Good Governance</strong><a href="https://kairos.io/blog/2025/08/08/growing-stronger-introducing-commercial-support-for-kairos/#1-good-governance" class="hash-link" aria-label="Direct link to 1-good-governance" title="Direct link to 1-good-governance" translate="no">​</a></h3>
<p>A mature open-source project needs a clear structure, transparency, and community direction. You want to know that decisions aren't made behind closed doors, and that the project will be around for the long term.</p>
<p>We're proud to say that <a href="https://kairos.io/blog/2024/10/08/kairos-joins-the-cncf-as-a-sandbox-project/" target="_blank" rel="noopener noreferrer" class=""><strong>Kairos achieved this last year</strong></a>, when it became a <a href="https://www.cncf.io/sandbox-projects/" target="_blank" rel="noopener noreferrer" class="">CNCF Sandbox Project</a>. This step formalized our commitment to open governance and alignment with the broader cloud-native ecosystem.</p>
<p>Joining the CNCF means more than just a badge—it puts Kairos on a clear track for growth and maturity, with expectations around documentation, contributor diversity, quality, and more. We're not building in isolation—we're growing with a strong open foundation.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="2-professional-support-options">2. <strong>Professional Support Options</strong><a href="https://kairos.io/blog/2025/08/08/growing-stronger-introducing-commercial-support-for-kairos/#2-professional-support-options" class="hash-link" aria-label="Direct link to 2-professional-support-options" title="Direct link to 2-professional-support-options" translate="no">​</a></h3>
<p>Even the best community can't always meet the needs of production environments. Some organizations—especially those in regulated industries or enterprise IT—need a guaranteed path to support when something breaks.</p>
<p>Until now, support for Kairos has been best-effort, through GitHub issues, Slack discussions, and community help. That's still available, and it works well for many teams.</p>
<p>But for those who need enterprise-grade support, we now have an answer.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="announcing-commercial-support-for-kairos">Announcing Commercial Support for Kairos<a href="https://kairos.io/blog/2025/08/08/growing-stronger-introducing-commercial-support-for-kairos/#announcing-commercial-support-for-kairos" class="hash-link" aria-label="Direct link to Announcing Commercial Support for Kairos" title="Direct link to Announcing Commercial Support for Kairos" translate="no">​</a></h2>
<p>Kairos now has <strong>official enterprise-grade support options</strong>, thanks to our support partner: <a href="https://www.spectrocloud.com/solutions/kairos-support" target="_blank" rel="noopener noreferrer" class="">Spectro Cloud</a>. As a major contributor and original creator of the project, Spectro Cloud is in a strong position to help organizations adopt Kairos with confidence.</p>
<p>Their support offerings range from basic ticketing-based assistance to full 24×7 production support, including hotfixes, CVE patching, onboarding, and SLAs. This is ideal for teams who want to standardize on Kairos at scale, and need more than community-based help.</p>
<p>This move does not change the open-source nature of the project—Kairos remains 100% open, with no commercial forks or gated features. It simply expands the ecosystem and offers more choice to adopters.</p>
<div class="buttons astro-7XAARZHW"><a id="quickstart" href="https://www.spectrocloud.com/solutions/kairos-support" class="astro-7XAARZHW"><p>Learn more</p></a></div>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-this-matters-even-if-you-dont-need-support">Why This Matters (Even If You Don't Need Support)<a href="https://kairos.io/blog/2025/08/08/growing-stronger-introducing-commercial-support-for-kairos/#why-this-matters-even-if-you-dont-need-support" class="hash-link" aria-label="Direct link to Why This Matters (Even If You Don't Need Support)" title="Direct link to Why This Matters (Even If You Don't Need Support)" translate="no">​</a></h2>
<p>You might be thinking, "I use Kairos just fine without needing a support contract. Why should this matter to me?”</p>
<p>Here's why:</p>
<ul>
<li class=""><strong>It strengthens the project</strong>. When support partners invest in Kairos, it helps sustain long-term development and community health.</li>
<li class=""><strong>It builds trust</strong>. Organizations that rely on SLAs or need commercial assurances now have a clearer path to adoption.</li>
<li class=""><strong>It keeps options open</strong>. Whether you're using Kairos as a solo developer or deploying across thousands of edge devices, you now have the flexibility to get help when you need it.</li>
</ul>
<p>Open source isn't just about free (as in beer) software. It's about freedom—of choice, of contribution, and of collaboration.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-next">What's Next?<a href="https://kairos.io/blog/2025/08/08/growing-stronger-introducing-commercial-support-for-kairos/#whats-next" class="hash-link" aria-label="Direct link to What's Next?" title="Direct link to What's Next?" translate="no">​</a></h2>
<p>This milestone is just one step in a broader journey.</p>
<p>We want to continue maturing Kairos and <strong>reach CNCF Incubation</strong>—a critical next phase in the project's evolution. To do that, we need to keep growing the community, broadening adoption, and building deeper collaboration.</p>
<p>So we're putting out a call:</p>
<p>🔔 <strong>If you're a company invested in Kairos</strong>, there are two key ways you can help:</p>
<ol>
<li class="">
<p><strong>Contribute Maintainers</strong><br>
<!-- -->If you're already using Kairos in your products or infrastructure, chances are you're making improvements, tooling, or fixes internally. Why not share that value with the broader community? We invite you to become a maintainer, help guide the roadmap, and collaborate with us to shape the future of edge Linux together.</p>
</li>
<li class="">
<p><strong>Become a Support Partner</strong><br>
<!-- -->If you're recommending Kairos to your customers and helping them succeed with it, we'd love to recognize your role. Let's work together to include your organization in our list of <strong>Kairos support partners</strong>—making it clear that help is available from more than one source, and encouraging adoption from companies that want a trusted hand.</p>
</li>
</ol>
<p>📩 <strong>Interested? Reach out to us at <a href="mailto:members@kairos.io" target="_blank" rel="noopener noreferrer" class="">members@kairos.io</a></strong> to start the conversation.</p>
<p>Let's continue building Kairos as an open, shared foundation—one that scales with our collective ambition.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="try-kairos--and-get-help-when-you-need-it">Try Kairos — and Get Help When You Need It<a href="https://kairos.io/blog/2025/08/08/growing-stronger-introducing-commercial-support-for-kairos/#try-kairos--and-get-help-when-you-need-it" class="hash-link" aria-label="Direct link to Try Kairos — and Get Help When You Need It" title="Direct link to Try Kairos — and Get Help When You Need It" translate="no">​</a></h2>
<p>If you're exploring Kairos or already using it in production, we're here to support you—both as a community and through professional channels.</p>
<p>Kairos now has <strong>official enterprise-grade support partners</strong>, for those who need additional help beyond the community. <a href="https://www.spectrocloud.com/solutions/kairos-support" target="_blank" rel="noopener noreferrer" class="">Spectro Cloud</a>, the original creator and a key maintainer of the project, is the first company to offer commercial support for Kairos.</p>
<p>We expect more organizations to join as support providers as adoption continues to grow.</p>
<p>As always, you can get involved with Kairos via <a href="https://github.com/kairos-io" target="_blank" rel="noopener noreferrer" class="">GitHub</a>, our <a href="https://kairos.io/community" target="_blank" rel="noopener noreferrer" class="">Slack community</a>, and other open channels. We welcome contributors, feedback, and discussion.</p>
<p>Thanks to everyone who's helped bring Kairos this far—we're excited to keep improving it with you.</p>
<p>🧡 The Kairos Maintainers</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Kairos release v3.5.0]]></title>
            <link>https://kairos.io/blog/2025/07/25/kairos-release-v3.5.0/</link>
            <guid>https://kairos.io/blog/2025/07/25/kairos-release-v3.5.0/</guid>
            <pubDate>Fri, 25 Jul 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Kairos release v3.5.0]]></description>
            <content:encoded><![CDATA[<h1 align="center"><br><img width="184" alt="kairos-white-column 5bc2fe34" src="https://user-images.githubusercontent.com/2420543/215073247-96988fd1-7fcf-4877-a28d-7c5802db43ab.png"><br><br></h1>
<p>We're excited to announce the release of Kairos 3.5.0! This release represents a significant milestone for the broader Kairos ecosystem, marking the completion of several key features across multiple projects that work together to improve the overall Kairos experience.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="️-meet-the-kairos-operator">⚙️ Meet the Kairos Operator<a href="https://kairos.io/blog/2025/07/25/kairos-release-v3.5.0/#%EF%B8%8F-meet-the-kairos-operator" class="hash-link" aria-label="Direct link to ⚙️ Meet the Kairos Operator" title="Direct link to ⚙️ Meet the Kairos Operator" translate="no">​</a></h2>
<p>The biggest addition to the Kairos ecosystem is the <strong>Kairos operator</strong> - a standalone Kubernetes operator that provides a native way to manage upgrades and operations on Kairos nodes. While this operator can work with previous Kairos versions, 3.5.0 marks the point where we consider it mature enough to be the recommended approach for Kubernetes-based management.</p>
<p>The operator provides two custom resources:</p>
<ul>
<li class="">
<p><strong>NodeOp</strong>: For generic operations on Kubernetes nodes (Kairos or not). It allows mounting the host's root filesystem to perform operations or run scripts.</p>
</li>
<li class="">
<p><strong>NodeOpUpgrade</strong>: A Kairos-specific custom resource for upgrading Kairos nodes. It automatically creates a NodeOp with the appropriate upgrade script and configuration.</p>
</li>
</ul>
<p>This means you can now manage your Kairos nodes using familiar Kubernetes patterns. The operator automatically detects Kairos nodes and labels them with <code>kairos.io/managed: true</code>, making it easy to target Kairos nodes specifically in hybrid clusters.</p>
<p>To get started with the operator, simply deploy it to your cluster:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token plain">kubectl apply </span><span class="token parameter variable" style="color:#36acaa">-k</span><span class="token plain"> https://github.com/kairos-io/kairos-operator/config/default</span><br></div></code></pre></div></div>
<p>Then trigger an upgrade by creating a NodeOpUpgrade resource:</p>
<div class="language-yaml codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-yaml codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token key atrule" style="color:#00a4db">apiVersion</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> operator.kairos.io/v1alpha1</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">kind</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> NodeOpUpgrade</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">metadata</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">name</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> kairos</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">upgrade</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">namespace</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> default</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">spec</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">image</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> quay.io/kairos/ubuntu</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain">22.04</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">standard</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">amd64</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">generic</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">v3.5.0</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">k3s</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">v1.33.2</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">k3s1</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">nodeSelector</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token key atrule" style="color:#00a4db">matchLabels</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token key atrule" style="color:#00a4db">kairos.io/managed</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"true"</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">concurrency</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> </span><span class="token number" style="color:#36acaa">1</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">stopOnFailure</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean important" style="color:#36acaa">true</span><br></div></code></pre></div></div>
<p>For more details on using the operator, check out our <a class="" href="https://kairos.io/operator-docs/">Kairos Operator documentation</a>.</p>
<p>The Kairos operator opens up new possibilities for node management. You can now:</p>
<ul>
<li class="">Perform custom operations on nodes using NodeOp resources</li>
<li class="">Control upgrade concurrency and failure handling</li>
<li class="">Apply configuration changes after installation</li>
<li class="">Reset nodes with custom configurations</li>
<li class="">Handle trusted boot upgrades through Kubernetes</li>
</ul>
<p>The operator provides fine-grained control over deployment strategies, allowing you to implement canary deployments, rolling updates, or bulk operations depending on your needs.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-enhanced-auroraboot-experience">🔧 Enhanced AuroraBoot Experience<a href="https://kairos.io/blog/2025/07/25/kairos-release-v3.5.0/#-enhanced-auroraboot-experience" class="hash-link" aria-label="Direct link to 🔧 Enhanced AuroraBoot Experience" title="Direct link to 🔧 Enhanced AuroraBoot Experience" translate="no">​</a></h2>
<p>Another significant milestone is the completion of the API-based workflow in <a href="https://github.com/kairos-io/AuroraBoot" target="_blank" rel="noopener noreferrer" class="">AuroraBoot</a>, our tool for building bootable images. AuroraBoot provides a comprehensive solution for creating custom bootable images, with both a user-friendly WebUI and powerful automation capabilities.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="introducing-auroraboot-webui">Introducing AuroraBoot WebUI<a href="https://kairos.io/blog/2025/07/25/kairos-release-v3.5.0/#introducing-auroraboot-webui" class="hash-link" aria-label="Direct link to Introducing AuroraBoot WebUI" title="Direct link to Introducing AuroraBoot WebUI" translate="no">​</a></h3>
<p>AuroraBoot includes a web-based interface that makes image building accessible to everyone. The WebUI provides an intuitive way to configure and build custom Kairos images without needing to remember complex command-line parameters. You can easily specify container images, cloud configurations, and various build options through a clean, modern interface.</p>
<div class="theme-admonition theme-admonition-warning admonition_xJq3 alert alert--warning"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.893 1.5c-.183-.31-.52-.5-.887-.5s-.703.19-.886.5L.138 13.499a.98.98 0 0 0 0 1.001c.193.31.53.501.886.501h13.964c.367 0 .704-.19.877-.5a1.03 1.03 0 0 0 .01-1.002L8.893 1.5zm.133 11.497H6.987v-2.003h2.039v2.003zm0-3.004H6.987V5.987h2.039v4.006z"></path></svg></span>Experimental Feature</div><div class="admonitionContent_BuS1"><p>The AuroraBoot WebUI is currently under heavy development and should be considered experimental. While functional, it may have limitations and could undergo significant changes in future releases. For production use, we recommend using the command-line interface.</p></div></div>
<p>To get started with the AuroraBoot WebUI, simply run:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">docker</span><span class="token plain"> run </span><span class="token parameter variable" style="color:#36acaa">--rm</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">-v</span><span class="token plain"> /var/run/docker.sock:/var/run/docker.sock </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">           </span><span class="token parameter variable" style="color:#36acaa">--privileged</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">           </span><span class="token parameter variable" style="color:#36acaa">-v</span><span class="token plain"> </span><span class="token environment constant" style="color:#36acaa">$PWD</span><span class="token plain">/build/:/output </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">           </span><span class="token parameter variable" style="color:#36acaa">-p</span><span class="token plain"> </span><span class="token number" style="color:#36acaa">8080</span><span class="token plain">:8080 </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">           quay.io/kairos/auroraboot web</span><br></div></code></pre></div></div>
<p>Then visit <code>http://localhost:8080</code> in your browser to access the interface. For more details on using the WebUI, check out our <a class="" href="https://kairos.io/docs/reference/auroraboot/">AuroraBoot documentation</a>.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="api-based-automation">API-Based Automation<a href="https://kairos.io/blog/2025/07/25/kairos-release-v3.5.0/#api-based-automation" class="hash-link" aria-label="Direct link to API-Based Automation" title="Direct link to API-Based Automation" translate="no">​</a></h3>
<p>The new API-based workflow in AuroraBoot enables automation of image building operations. This means you can now integrate image building into your CI/CD pipelines and infrastructure automation workflows. The API provides programmatic access to all AuroraBoot features, allowing you to build images as part of your automated deployment processes.</p>
<p>The API workflow complements the existing WebUI, giving you both the ease of use for manual operations and the power of automation for production environments.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-configuration-path-migration-reminder">📁 Configuration Path Migration Reminder<a href="https://kairos.io/blog/2025/07/25/kairos-release-v3.5.0/#-configuration-path-migration-reminder" class="hash-link" aria-label="Direct link to 📁 Configuration Path Migration Reminder" title="Direct link to 📁 Configuration Path Migration Reminder" translate="no">​</a></h2>
<p>While <a href="https://github.com/kairos-io/kairos/issues/2233" target="_blank" rel="noopener noreferrer" class="">the configuration path change</a> from <code>/etc/elemental/config.yaml</code> to <code>/etc/kairos/config.yaml</code> has been moved to v4.0.0, we want to remind users to start migrating their configurations now. This change will align our configuration paths with the Kairos branding and provide a cleaner, more consistent experience.</p>
<p>If you're using the old path, we recommend updating your configurations to use the new location (<code>/etc/kairos/config.yaml</code>) to prepare for deprecation. The old path will continue to work for now, but migrating early will ensure a smooth transition.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-whats-next">🔮 What's Next<a href="https://kairos.io/blog/2025/07/25/kairos-release-v3.5.0/#-whats-next" class="hash-link" aria-label="Direct link to 🔮 What's Next" title="Direct link to 🔮 What's Next" translate="no">​</a></h2>
<p>The completion of these ecosystem features represents a significant step toward more integrated and automated Kairos workflows. We're excited to see how the community uses these new capabilities to build more sophisticated deployment and management workflows.</p>
<p>We're already working on the next milestone - <a href="https://github.com/kairos-io/kairos/issues/2990" target="_blank" rel="noopener noreferrer" class="">Kairos v3.6.0</a>. Check out the ticket to see what's coming next.</p>
<p>As always, we encourage you to try out the new features and share your feedback. Whether you're upgrading existing clusters, automating image builds, or deploying new ones, these tools should make your day-to-day operations smoother and more predictable.</p>
<p>For a complete list of changes in this release, visit the <a href="https://github.com/kairos-io/kairos/releases/tag/v3.5.0" target="_blank" rel="noopener noreferrer" class="">v3.5.0 release page on GitHub</a>. For detailed upgrade instructions and examples, visit our <a class="" href="https://kairos.io/docs/upgrade/">upgrade documentation</a>. If you run into any issues or have questions, join the conversation in our <a href="https://slack.cncf.io/#kairos" target="_blank" rel="noopener noreferrer" class="">Slack</a> or <a href="https://github.com/kairos-io/kairos/discussions" target="_blank" rel="noopener noreferrer" class="">GitHub Discussions</a>. If you want to participate in the development process, you can always join our <a href="https://kairos.io/community/" target="_blank" rel="noopener noreferrer" class="">office hours</a> - the calendar is available on our community page.</p>
<p>Happy upgrading!</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Kairos release v3.4.0]]></title>
            <link>https://kairos.io/blog/2025/04/24/kairos-release-v3.4.0/</link>
            <guid>https://kairos.io/blog/2025/04/24/kairos-release-v3.4.0/</guid>
            <pubDate>Thu, 24 Apr 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Kairos release v3.4.0]]></description>
            <content:encoded><![CDATA[<h1 align="center"><br><img width="184" alt="kairos-white-column 5bc2fe34" src="https://user-images.githubusercontent.com/2420543/215073247-96988fd1-7fcf-4877-a28d-7c5802db43ab.png"><br><br></h1>
<p>Every now and then, a release isn't just a version bump—it’s a reset button. Kairos 3.4.0 is one of those releases.</p>
<p>In the last few months, we’ve been heads-down rethinking what makes Kairos powerful, approachable, and future-proof. The result is a foundational overhaul: a brand-new build system, native images for all major cloud providers, streamlined customization through system extensions, and a tighter Kubernetes story with built-in support for k0s. This release isn’t just packed with features—it reflects where the project is heading and how our community is shaping that direction.</p>
<p>Let’s walk through the biggest milestones in Kairos 3.4.0, how they work, and why they matter.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="️-rebuilding-kairos-from-the-ground-up-with-kairos-init">🛠️ Rebuilding Kairos from the Ground Up with <code>kairos-init</code><a href="https://kairos.io/blog/2025/04/24/kairos-release-v3.4.0/#%EF%B8%8F-rebuilding-kairos-from-the-ground-up-with-kairos-init" class="hash-link" aria-label="Direct link to ️-rebuilding-kairos-from-the-ground-up-with-kairos-init" title="Direct link to ️-rebuilding-kairos-from-the-ground-up-with-kairos-init" translate="no">​</a></h2>
<p>We’ve officially said goodbye to Earthly and rebuilt the Kairos build system from scratch. The new system, centered around <code>kairos-init</code>, is faster, cleaner, and deeply inspired by the declarative configuration model we’ve honed through Yip.</p>
<blockquote>
<p>“We didn’t just want to make the build system better—we wanted to make it understandable and hackable.” — from <a href="https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/" target="_blank" rel="noopener noreferrer" class="">our deep dive</a></p>
</blockquote>
<p>This change makes it easier than ever to create your own derivative OS with Kairos. If you’re customizing images or building new flavors, the <a href="https://kairos.io/docs/reference/kairos-factory/" target="_blank" rel="noopener noreferrer" class=""><code>kairos-factory</code> documentation</a> is your new best friend. It’s built for composability, consistency, and speed.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="️-kairos-goes-native-on-the-cloud">☁️ Kairos Goes Native on the Cloud<a href="https://kairos.io/blog/2025/04/24/kairos-release-v3.4.0/#%EF%B8%8F-kairos-goes-native-on-the-cloud" class="hash-link" aria-label="Direct link to ☁️ Kairos Goes Native on the Cloud" title="Direct link to ☁️ Kairos Goes Native on the Cloud" translate="no">​</a></h2>
<p>With 3.4.0, Kairos now offers <strong>official cloud images</strong> for AWS, Azure, and GCP. That means you can deploy Kairos right from your cloud console—no manual image imports, no extra setup.</p>
<ul>
<li class=""><a href="https://kairos.io/docs/installation/aws/" target="_blank" rel="noopener noreferrer" class="">Launch on AWS</a></li>
<li class=""><a href="https://kairos.io/docs/installation/azure/" target="_blank" rel="noopener noreferrer" class="">Deploy via Azure Marketplace</a></li>
<li class=""><a href="https://kairos.io/docs/installation/gce/" target="_blank" rel="noopener noreferrer" class="">Spin up on GCP</a></li>
</ul>
<p>This makes it easier to integrate Kairos into hybrid, multi-cloud, or CI-driven workflows—and aligns with our goal to make Kairos ready-to-go for every environment.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-kubernetes-with-k0s-the-meta-distribution-vision">🚀 Kubernetes with k0s: The Meta-Distribution Vision<a href="https://kairos.io/blog/2025/04/24/kairos-release-v3.4.0/#-kubernetes-with-k0s-the-meta-distribution-vision" class="hash-link" aria-label="Direct link to 🚀 Kubernetes with k0s: The Meta-Distribution Vision" title="Direct link to 🚀 Kubernetes with k0s: The Meta-Distribution Vision" translate="no">​</a></h2>
<p>With native support for <a href="https://k0sproject.io/" target="_blank" rel="noopener noreferrer" class="">k0s</a>, Kairos is now a <strong>meta-distribution for Kubernetes</strong>—fully declarative, fully integrated. Whether you're deploying edge nodes or building HA clusters, k0s + Kairos is a minimal, clean foundation.</p>
<p>You can now toggle between k3s and k0s setups in the updated docs and configure each using the same Kairos cloud-init model.<br>
<!-- -->👉 <a href="https://kairos.io/blog/2025/04/02/kairos-meets-k0s-a-meta-distribution-for-kubernetes-is-born/" target="_blank" rel="noopener noreferrer" class="">Blog deep dive</a></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-live-customization-with-system-extensions">🧩 Live Customization with System Extensions<a href="https://kairos.io/blog/2025/04/24/kairos-release-v3.4.0/#-live-customization-with-system-extensions" class="hash-link" aria-label="Direct link to 🧩 Live Customization with System Extensions" title="Direct link to 🧩 Live Customization with System Extensions" translate="no">​</a></h2>
<p>Say goodbye to image rebuilds for small tweaks. System extensions let you declaratively <strong>add or modify behavior on a running Kairos system</strong>, and 3.4.0 ships with built-in CLI support to install, remove, enable, and disable extensions.</p>
<p>👉 <a href="https://kairos.io/blog/2025/04/15/system-extensions-simplified-live-customization-with-kairos/" target="_blank" rel="noopener noreferrer" class="">Learn more</a><br>
<!-- -->👉 <a href="https://kairos.io/docs/advanced/sys-extensions/" target="_blank" rel="noopener noreferrer" class="">System Extensions docs</a></p>
<p>This opens the door to layered, profile-based systems that evolve post-deployment—great for both immutable infrastructure and rapidly changing environments.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-new-contributor-shout-out">🙌 New Contributor Shout-Out<a href="https://kairos.io/blog/2025/04/24/kairos-release-v3.4.0/#-new-contributor-shout-out" class="hash-link" aria-label="Direct link to 🙌 New Contributor Shout-Out" title="Direct link to 🙌 New Contributor Shout-Out" translate="no">​</a></h2>
<p>Huge thanks to <strong>@jimmycathy</strong> for their first contribution to the project! 🎉<br>
<!-- -->PR: <a href="https://github.com/kairos-io/kairos/pull/3255" target="_blank" rel="noopener noreferrer" class="">https://github.com/kairos-io/kairos/pull/3255</a></p>
<p>We’re always excited to welcome new contributors. Whether it’s documentation, ideas, or PRs—every bit helps make Kairos stronger for everyone.</p>
<hr>
<p>Stay tuned as we continue evolving Kairos with your feedback and use cases in mind. Got a question or want to share how you’re using 3.4.0? Join the conversation in our <a href="https://kairos.io/community/" target="_blank" rel="noopener noreferrer" class="">Discord</a> or <a href="https://github.com/kairos-io/kairos/discussions" target="_blank" rel="noopener noreferrer" class="">GitHub Discussions</a>.</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[System Extensions, Simplified: Live Customization with Kairos]]></title>
            <link>https://kairos.io/blog/2025/04/15/system-extensions-simplified-live-customization-with-kairos/</link>
            <guid>https://kairos.io/blog/2025/04/15/system-extensions-simplified-live-customization-with-kairos/</guid>
            <pubDate>Tue, 15 Apr 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Introducing the new CLI-driven system extension management in Kairos. Download, enable, and manage system extensions live without rebuilding your OS image.]]></description>
            <content:encoded><![CDATA[<p>Kairos has always focused on making operating system deployments more predictable, reproducible, and manageable—especially in edge and embedded environments. But for all the benefits of immutability, one challenge has lingered:</p>
<blockquote>
<p><strong>How do you safely and easily customize a system after it’s built—without breaking the image or going full Dockerfile rebuild?</strong></p>
</blockquote>
<p>Today, we’re introducing a much cleaner answer: <strong>the new system extension management framework</strong>, now available via the Kairos Agent CLI and when Kairos 3.4.x releases.</p>
<hr>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-whats-new">💡 What's New<a href="https://kairos.io/blog/2025/04/15/system-extensions-simplified-live-customization-with-kairos/#-whats-new" class="hash-link" aria-label="Direct link to 💡 What's New" title="Direct link to 💡 What's New" translate="no">​</a></h2>
<p>System extensions in Kairos are not new—but managing them used to be a manual process. You had to mount things yourself, know where to drop files, and keep track of boot profiles by hand.</p>
<p>That’s all changed.</p>
<p>You can now:</p>
<ul>
<li class="">🔄 <strong>Download</strong> raw extension images over <code>https</code>, <code>file</code>, or even <code>oci</code> (alpha)</li>
<li class="">✅ <strong>Enable or disable</strong> extensions declaratively per boot profile</li>
<li class="">⚡ <strong>Activate extensions live</strong> with <code>--now</code></li>
<li class="">🔍 <strong>List</strong> which extensions are installed or currently active</li>
<li class="">🧹 <strong>Remove</strong> extensions safely—links and all</li>
</ul>
<p>All from one CLI entrypoint:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token plain">kairos-agent sysext</span><br></div></code></pre></div></div>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="️-how-it-works">🗂️ How It Works<a href="https://kairos.io/blog/2025/04/15/system-extensions-simplified-live-customization-with-kairos/#%EF%B8%8F-how-it-works" class="hash-link" aria-label="Direct link to 🗂️ How It Works" title="Direct link to 🗂️ How It Works" translate="no">​</a></h2>
<p>Under the hood, the new system works using a simple but powerful layout:</p>
<table><thead><tr><th>Path</th><th>What it does</th></tr></thead><tbody><tr><td><code>/var/lib/kairos/extensions/</code></td><td>Stores downloaded disk images</td></tr><tr><td><code>.../active</code>, <code>.../passive</code>, etc.</td><td>Symlink folders tied to boot profiles</td></tr><tr><td><code>/run/extensions/</code></td><td>Where active sysexts live at runtime</td></tr></tbody></table>
<p>When the system boots, <strong><code>immucore</code></strong> checks the current boot profile and links the relevant extensions into <code>/run/extensions/</code>, which are then loaded by <strong><code>systemd-sysext</code></strong>.</p>
<p>It’s all ephemeral, safe, and declarative.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-compatible-with-trusted-boot">🔐 Compatible with Trusted Boot<a href="https://kairos.io/blog/2025/04/15/system-extensions-simplified-live-customization-with-kairos/#-compatible-with-trusted-boot" class="hash-link" aria-label="Direct link to 🔐 Compatible with Trusted Boot" title="Direct link to 🔐 Compatible with Trusted Boot" translate="no">​</a></h2>
<p>System security remains a top priority in Kairos. If you’re using <strong>Trusted Boot</strong>, rest assured: this new extension mechanism doesn't compromise your system's integrity.</p>
<p>Only <strong>signed and trusted extension images</strong> are allowed to load. This means:</p>
<ul>
<li class="">The bootloader and init system verify authenticity</li>
<li class="">Unsigned or tampered images are simply ignored</li>
<li class="">Your measured boot chain remains intact and auditable</li>
</ul>
<p>So yes—you can safely extend your system at runtime <em>without sacrificing security</em>.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="️-real-world-usage">🛠️ Real-World Usage<a href="https://kairos.io/blog/2025/04/15/system-extensions-simplified-live-customization-with-kairos/#%EF%B8%8F-real-world-usage" class="hash-link" aria-label="Direct link to 🛠️ Real-World Usage" title="Direct link to 🛠️ Real-World Usage" translate="no">​</a></h2>
<p>Here’s what it looks like in action:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic"># Download a disk image directly</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">kairos-agent sysext download https://example.org/extensions/mytool.img</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># Enable it for active boots, and load it now</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">kairos-agent sysext </span><span class="token builtin class-name">enable</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">--active</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">--now</span><span class="token plain"> mytool</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># See what’s active</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">kairos-agent sysext list </span><span class="token parameter variable" style="color:#36acaa">--active</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># Remove it completely</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">kairos-agent sysext remove </span><span class="token parameter variable" style="color:#36acaa">--now</span><span class="token plain"> mytool</span><br></div></code></pre></div></div>
<p>And yes—<strong>you don’t need to type full names</strong>. All sysext commands accept <strong>regex patterns</strong>. That means <code>mytool</code> will match something like <code>mytool-v1.0.sysext.raw</code>.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-looking-ahead">🚧 Looking Ahead<a href="https://kairos.io/blog/2025/04/15/system-extensions-simplified-live-customization-with-kairos/#-looking-ahead" class="hash-link" aria-label="Direct link to 🚧 Looking Ahead" title="Direct link to 🚧 Looking Ahead" translate="no">​</a></h2>
<p>This is just the beginning. We're planning further enhancements to system extension workflows—like declarative integration in the config layer, improved OCI support, and better visibility tooling.</p>
<p>We’d love to hear how you use it—and what would make it even better. Jump into <a href="https://kairos.io/community/" target="_blank" rel="noopener noreferrer" class="">the Kairos community</a> and let us know what you think.</p>
<p>For a more detailed breakdown, including supported commands and advanced examples, check out the <a href="https://kairos.io/docs/advanced/sys-extensions/" target="_blank" rel="noopener noreferrer" class="">System Extensions documentation</a>.</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Kairos Meets k0s: A Meta-Distribution for Kubernetes is Born]]></title>
            <link>https://kairos.io/blog/2025/04/02/kairos-meets-k0s-a-meta-distribution-for-kubernetes-is-born/</link>
            <guid>https://kairos.io/blog/2025/04/02/kairos-meets-k0s-a-meta-distribution-for-kubernetes-is-born/</guid>
            <pubDate>Wed, 02 Apr 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Up until now, Kairos has shipped with first-class support for k3s out of the box. If you wanted something else? You had to rely on community-powered providers. And let’s be honest, while amazing in their own right, they’ve been... fragmented.]]></description>
            <content:encoded><![CDATA[<p>Up until now, Kairos has shipped with first-class support for k3s out of the box. If you wanted something else? You had to rely on community-powered providers. And let’s be honest, while amazing in their own right, they’ve been... fragmented.</p>
<p>We’ve seen providers emerge for <code>kubeadm</code>, <code>nodeadm</code>, <code>microk8s</code>, and even another flavor of <code>k3s</code>. Each one added the ability to run Kubernetes on Kairos, but they were often self-contained efforts. Most didn’t plug into our cloud-init-style configuration, which meant you had to know your way around their specific setup to get them running. Power users and contributors made them work, but new users? Not so much.</p>
<p>Then there’s the <a href="https://github.com/kairos-io/provider-kairos" target="_blank" rel="noopener noreferrer" class=""><code>provider-kairos</code></a>, which offers a consistent configuration layer across setups and makes Kubernetes orchestration a breeze, especially for decentralized, peer-to-peer deployments powered by EdgeVPN. But it had one limitation: it only worked with <code>k3s</code>.</p>
<p>That is... until now.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="enter-k0s-the-zero-friction-kubernetes">Enter k0s: The Zero Friction Kubernetes<a href="https://kairos.io/blog/2025/04/02/kairos-meets-k0s-a-meta-distribution-for-kubernetes-is-born/#enter-k0s-the-zero-friction-kubernetes" class="hash-link" aria-label="Direct link to Enter k0s: The Zero Friction Kubernetes" title="Direct link to Enter k0s: The Zero Friction Kubernetes" translate="no">​</a></h2>
<p>A few months back, <a href="https://www.linkedin.com/in/william-rizzo/" target="_blank" rel="noopener noreferrer" class="">William Rizzo</a>, a CNCF and Linkerd Ambassador, approached us with a pull request and a mission: bring <code>k0s</code> to Kairos with the same first-class integration as <code>k3s</code>.</p>
<p>For those unfamiliar, <a href="https://docs.k0sproject.io/stable/" target="_blank" rel="noopener noreferrer" class="">k0s</a> is a lightweight, CNCF-certified Kubernetes distribution that bundles everything into a single binary. No OS dependencies. No frills. Just Kubernetes, as it should be — simple to run, easy to maintain, and friendly across bare metal, cloud, edge, and IoT. It supports containerd, Kube-Router by default (with optional Calico), and can run anywhere Linux does. It’s perfect for Kairos.</p>
<p>We sat down together and made it happen. This is the magic of open-source: two CNCF Sandbox Projects, <a href="https://kairos.io/" target="_blank" rel="noopener noreferrer" class="">Kairos</a> and <a href="https://k0sproject.io/" target="_blank" rel="noopener noreferrer" class="">k0s</a>, coming together to build something bigger than either could alone.</p>
<p>Now, thanks to this collaboration, you can run <code>k0s</code> using the same Kairos-native cloud-init configuration that previously only supported <code>k3s</code>. That means P2P cluster formation with EdgeVPN, full configuration via YAML, and all the DX goodness you’re used to, with a new Kubernetes engine under the hood.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-this-means">What This Means<a href="https://kairos.io/blog/2025/04/02/kairos-meets-k0s-a-meta-distribution-for-kubernetes-is-born/#what-this-means" class="hash-link" aria-label="Direct link to What This Means" title="Direct link to What This Means" translate="no">​</a></h2>
<p>Kairos just leveled up.</p>
<p>We’re not just a Linux meta-distribution anymore. We’re taking our first real steps into becoming a Kubernetes <em>meta</em>-distribution.</p>
<p>So meta.</p>
<p><img decoding="async" loading="lazy" src="https://github.com/user-attachments/assets/5fe0fe0c-7962-4dad-9c27-cf6aab23af11" alt="Always has been" class="img_ev3q"></p>
<p>From now on, users don’t have to choose between clean, declarative setups and their preferred Kubernetes flavor. The Kairos provider now supports both <code>k3s</code> <em>and</em> <code>k0s</code> natively. Want to try it? We’ve added <a href="https://kairos.io/docs/examples/" target="_blank" rel="noopener noreferrer" class="">examples</a> to our repository showing both side-by-side so you can pick the flavor that suits your use case best.</p>
<p>And it doesn’t stop there. As noted in the recent <a href="https://www.cncf.io/blog/2025/03/25/building-secure-kubernetes-edge-images-with-kairos-and-k0s/" target="_blank" rel="noopener noreferrer" class="">CNCF blog post</a>, combining <code>k0s</code>’s single-binary simplicity with Kairos’s secure, immutable images is a huge win for edge computing. Together, we’re making it easier to build secure-by-default, production-ready clusters from the ground up.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="try-it-today">Try it Today<a href="https://kairos.io/blog/2025/04/02/kairos-meets-k0s-a-meta-distribution-for-kubernetes-is-born/#try-it-today" class="hash-link" aria-label="Direct link to Try it Today" title="Direct link to Try it Today" translate="no">​</a></h2>
<p>The <code>k0s</code> integration will be fully stable in Kairos <code>v3.4</code>, but you don’t have to wait. It’s already available in our beta or nightly images for <a href="https://quay.io/repository/kairos/ubuntu" target="_blank" rel="noopener noreferrer" class="">Ubuntu</a>, <a href="https://quay.io/repository/kairos/rockylinux" target="_blank" rel="noopener noreferrer" class="">Rockylinux</a>, and <a href="https://quay.io/repository/kairos/opensuse" target="_blank" rel="noopener noreferrer" class="">openSUSE</a>, or you can <a href="https://kairos.io/docs/advanced/build/#auroraboot" target="_blank" rel="noopener noreferrer" class="">build your own with AuroraBoot</a>.</p>
<p>To get started:</p>
<ul>
<li class="">Check out the <a href="https://github.com/kairos-io/provider-kairos" target="_blank" rel="noopener noreferrer" class="">Kairos provider repository</a></li>
<li class="">Explore the updated examples with <code>k3s</code> and <code>k0s</code></li>
<li class="">Spin up a custom image</li>
<li class="">And let us know what you build!</li>
</ul>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[How We Rebuilt Kairos building From the Ground Up]]></title>
            <link>https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/</link>
            <guid>https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/</guid>
            <pubDate>Wed, 26 Mar 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[🧱 Introduction]]></description>
            <content:encoded><![CDATA[<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-introduction">🧱 Introduction<a href="https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/#-introduction" class="hash-link" aria-label="Direct link to 🧱 Introduction" title="Direct link to 🧱 Introduction" translate="no">​</a></h2>
<p>Building Kairos has always been about more than assembling images — it's about shaping a flexible, powerful OS tailored for the edge. Over the past couple of years, we've learned a lot while navigating how to build and maintain Kairos across a growing list of base distributions, architectures, and board-specific targets.</p>
<p>Today, we’re excited to introduce something that marks a turning point in how Kairos is built: <strong><code>kairos-init</code></strong>.</p>
<p>This post isn't just about a new tool. It’s about simplifying complexity, rediscovering clarity, and embedding hard-earned lessons into something lean and extensible. If you've followed our journey, you'll know that we've gone from Dockerfiles to Earthly, and now to a new approach centered on declarative simplicity with Yip.</p>
<p>In this post, we’ll take you behind the scenes:</p>
<ul>
<li class="">Why the old ways worked (until they didn’t)</li>
<li class="">How we outgrew our tooling</li>
<li class="">What <code>kairos-init</code> changes — and why it matters</li>
</ul>
<p>This is the story of how we rebuilt the foundation of Kairos, one layer at a time.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-the-early-days-building-with-dockerfiles">🐳 The Early Days: Building with Dockerfiles<a href="https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/#-the-early-days-building-with-dockerfiles" class="hash-link" aria-label="Direct link to 🐳 The Early Days: Building with Dockerfiles" title="Direct link to 🐳 The Early Days: Building with Dockerfiles" translate="no">​</a></h2>
<p>When Kairos first took shape, our needs were simple. We wanted a predictable, repeatable way to turn a base Linux distribution into a fully working Kairos image. And at the time, the most straightforward path was through a set of handcrafted <strong>Dockerfiles</strong> — one for each supported base.</p>
<p>Need Kairos on Ubuntu? There was a Dockerfile for that. OpenSUSE? Another one. Want to tweak something for a Raspberry Pi or test an Alpine variant? Copy, paste, modify.</p>
<p>This worked — until it didn’t.</p>
<p>At first, it was empowering. We could iterate quickly, test changes, and get a Kairos image up and running in no time. Each Dockerfile acted like a scriptable recipe for image creation. But as we started expanding support for more:</p>
<ul>
<li class="">🧱 <strong>Distributions</strong> (Ubuntu 24.04, 22.04, 20.04, OpenSUSE, Alpine, Rocky, Fedora…)</li>
<li class="">📦 <strong>Releases</strong> (LTS, rolling, and experimental flavors across versions)</li>
<li class="">⚙️ <strong>Architectures</strong> (x86_64, ARM64)</li>
<li class="">📦 <strong>Boards and platforms</strong> (Raspberry Pi, NVIDIA Jetson, cloud providers…)</li>
</ul>
<p>… the number of Dockerfiles exploded.</p>
<p align="center"><img src="https://kairos.io/img/init-1.png" alt="Kairos Dockerfiles in the wild (Version 2.3.0)"><br><em>Kairos Dockerfiles in the wild (Version 2.3.0)</em></p>
<p><em>Kairos Dockerfiles in the wild (Version 2.3.0)</em></p>
<p>Maintaining them became a slow grind. Every distro had its quirks. Every version bump required tweaks. Repeating common steps across files introduced subtle bugs. And worst of all, it was hard to scale — we were reinventing the same process in N different places, each slightly different, each easy to break.</p>
<p>We needed a better way.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-scaling-painfully-enter-earthly">🌍 Scaling Painfully: Enter Earthly<a href="https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/#-scaling-painfully-enter-earthly" class="hash-link" aria-label="Direct link to 🌍 Scaling Painfully: Enter Earthly" title="Direct link to 🌍 Scaling Painfully: Enter Earthly" translate="no">​</a></h2>
<p>As the number of supported distros, architectures, and boards grew, so did the pain of managing our Dockerfiles. It wasn’t just about duplication anymore — it was about orchestration, coordination, and staying sane across a forest of moving parts.</p>
<p>So we took the next step and adopted <strong><a href="https://earthly.dev/" target="_blank" rel="noopener noreferrer" class="">Earthly</a></strong>.</p>
<p>Earthly gave us a powerful framework to unify and modularize our builds. Instead of one Dockerfile per case, we could define reusable steps, build pipelines, and cache logic across flavors and platforms. It brought real structure to our chaos.</p>
<p>With Earthly, we gained:</p>
<ul>
<li class="">🔁 <strong>Reusable modules</strong> for common build logic</li>
<li class="">🧩 <strong>Parameterized builds</strong> across distros and versions</li>
<li class="">🧠 <strong>Smarter caching</strong>, which cut build times drastically</li>
<li class="">🤖 <strong>Better CI integration</strong>, especially in GitHub Actions</li>
<li class="">🏗️ <strong>Cross-architecture support</strong> (building ARM images from x86 machines)</li>
</ul>
<p>It was a massive improvement. Kairos became easier to scale, easier to extend, and more robust in CI/CD pipelines. We could merge several Dockerfiles into a single one for that given Flavor and make earthly trigger the right steps based on the target architecture or version.</p>
<p align="center"><img src="https://kairos.io/img/init-2.png" alt="Less lines is always better, right? (Version 3.3.1)"><br><em>Less lines is always better, right? (Version 3.3.1)</em></p>
<p>But the cost of complexity caught up with us.</p>
<p>Earthly was powerful, but also heavy. Setting up the environment required more tooling and context. Onboarding new contributors meant explaining layers of build abstraction. And eventually, even Earthly couldn’t fully hide the fact that we were fighting the complexity we had slowly built up.</p>
<p>As our use cases expanded — with more devices, more customization, more flavors — our build logic became a tangled web of conditionals and overrides.</p>
<p align="center"><img src="https://kairos.io/img/init-3.png" alt="The Earthly pipeline grows instead (Version 3.3.1)"><br><em>The Earthly pipeline grows instead (Version 3.3.1)</em></p>
<p>We needed a reset. A system built from the start for clarity and adaptability.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-reaching-the-breaking-point">🧨 Reaching the Breaking Point<a href="https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/#-reaching-the-breaking-point" class="hash-link" aria-label="Direct link to 🧨 Reaching the Breaking Point" title="Direct link to 🧨 Reaching the Breaking Point" translate="no">​</a></h2>
<p>By this stage, we had all the signs of a powerful yet brittle system.</p>
<p>Every new board support request — whether for a Jetson device, RPi variant, or some obscure industrial box — meant another round of “how do we fit this into the Earthly pipeline without breaking 10 other things?” Even small changes to the build logic carried unintended ripple effects. Maintenance became a game of regression whack-a-mole.</p>
<p>Our internal complexity had quietly outpaced the benefits of our tooling.</p>
<ul>
<li class="">We were juggling <strong>multiple abstraction layers</strong></li>
<li class="">Supporting a new architecture meant rewriting or extending <strong>multiple Earthfiles</strong></li>
<li class="">Troubleshooting builds required context-switching between tools and environments</li>
<li class="">Most importantly, it became <strong>hard for contributors to participate</strong></li>
</ul>
<p>That’s when we stopped and asked: <em>What if we could start fresh?</em></p>
<p>The answer was <code>kairos-init</code>.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="️-we-tried-other-tools-first">🛠️ We Tried Other Tools First<a href="https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/#%EF%B8%8F-we-tried-other-tools-first" class="hash-link" aria-label="Direct link to 🛠️ We Tried Other Tools First" title="Direct link to 🛠️ We Tried Other Tools First" translate="no">​</a></h2>
<p>Before diving into <code>kairos-init</code>, we explored other tools and frameworks hoping to find a better fit. But none of them quite matched the specific constraints of our ecosystem — building across multiple distros, versions, and architectures in a consistent, maintainable way.</p>
<p>So, we did what every developer dreams of: we built our own.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-the-breakthrough-kairos-init-and-yip">✨ The Breakthrough: <code>kairos-init</code> and Yip<a href="https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/#-the-breakthrough-kairos-init-and-yip" class="hash-link" aria-label="Direct link to -the-breakthrough-kairos-init-and-yip" title="Direct link to -the-breakthrough-kairos-init-and-yip" translate="no">​</a></h2>
<p><code>kairos-init</code> is a CLI tool that encapsulates everything needed to transform <strong>any base Linux image</strong> into a fully Kairos system — with nothing more than a standard <code>Dockerfile</code>.</p>
<p>By running <code>kairos-init BUILD</code> in a Dockerfile, it:</p>
<ul>
<li class="">Inspects the base image</li>
<li class="">Generates a Yip configuration</li>
<li class="">Executes that config to:<!-- -->
<ul>
<li class="">Install necessary packages</li>
<li class="">Add the Kairos framework (binaries, configs, init hooks)</li>
<li class="">Patch the initramfs</li>
<li class="">Link kernel files</li>
<li class="">Apply any workarounds or tweaks</li>
</ul>
</li>
</ul>
<p>The result is a container image that’s Kairos-ready — no extra steps, no complex layering.</p>
<p>You can then:</p>
<ul>
<li class="">Use it as an <strong>upgrade image</strong></li>
<li class="">Extend it with Kubernetes runtimes like <code>k3s</code> or <code>k0s</code> using flags</li>
<li class="">Convert it into various formats with <a href="https://github.com/kairos-io/AuroraBoot" target="_blank" rel="noopener noreferrer" class="">AuroraBoot</a>:<!-- -->
<ul>
<li class="">ISO</li>
<li class="">Raw image</li>
<li class="">Cloud image</li>
<li class="">PXE bootable</li>
<li class="">EFI Unified System Image</li>
</ul>
</li>
</ul>
<p>And because it’s just a Dockerfile, it drops right into any existing workflow:</p>
<ul>
<li class="">CI/CD pipelines</li>
<li class="">Local testing</li>
<li class="">Version-controlled infra repos</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-a-cleaner-future">🌤 A Cleaner Future<a href="https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/#-a-cleaner-future" class="hash-link" aria-label="Direct link to 🌤 A Cleaner Future" title="Direct link to 🌤 A Cleaner Future" translate="no">​</a></h2>
<p>With <code>kairos-init</code>, we’ve:</p>
<ul>
<li class="">Simplified builds down to one step</li>
<li class="">Removed the need for Earthly or complex pipelines</li>
<li class="">Made Kairos accessible to new contributors and integrators</li>
<li class="">Enabled future growth without growing technical debt</li>
</ul>
<p>We’re no longer managing complexity — we’ve replaced it with clarity.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-whats-next">🔭 What’s Next<a href="https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/#-whats-next" class="hash-link" aria-label="Direct link to 🔭 What’s Next" title="Direct link to 🔭 What’s Next" translate="no">​</a></h2>
<p>What’s ahead:</p>
<ul>
<li class="">More <code>kairos-init</code> examples and docs</li>
<li class="">Deep dives on Yip</li>
<li class="">Custom build guides</li>
<li class="">Community use cases</li>
</ul>
<p>We’re also eager to hear how <strong>you</strong> use it — tag us, open issues, or just say hi.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="-conclusion">🧭 Conclusion<a href="https://kairos.io/blog/2025/03/26/how-we-rebuilt-kairos-building-from-the-ground-up/#-conclusion" class="hash-link" aria-label="Direct link to 🧭 Conclusion" title="Direct link to 🧭 Conclusion" translate="no">​</a></h2>
<p>From handcrafted Dockerfiles to Earthly-powered pipelines and now to a clean, declarative build system — this journey has been about making Kairos better not just for us, but for you.</p>
<p>With <code>kairos-init</code>, we’ve laid the groundwork for a more open, composable, and hackable future.</p>
<p>Thanks for building with us. 🚀</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[How I Automated My Doorbell with Kairos (and You Can Too)]]></title>
            <link>https://kairos.io/blog/2025/03/18/how-i-automated-my-doorbell-with-kairos-and-you-can-too/</link>
            <guid>https://kairos.io/blog/2025/03/18/how-i-automated-my-doorbell-with-kairos-and-you-can-too/</guid>
            <pubDate>Tue, 18 Mar 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Picture this: You’re deep in focus, coding away, and the doorbell rings. Except… you never hear it. The mailman leaves, and now your package is on an adventure you didn't plan for. That’s exactly what happened to me, so I did what any geek would do—turn my dumb doorbell into a smart one using Kairos.]]></description>
            <content:encoded><![CDATA[<p>Picture this: You’re deep in focus, coding away, and the doorbell rings. Except… you never hear it. The mailman leaves, and now your package is on an adventure you didn't plan for. That’s exactly what happened to me, so I did what any geek would do—turn my dumb doorbell into a smart one using Kairos.</p>
<!-- -->
<div class="theme-admonition theme-admonition-warning admonition_xJq3 alert alert--warning"><div class="admonitionHeading_Gvgb"><span class="admonitionIcon_Rf37"><svg viewBox="0 0 16 16"><path fill-rule="evenodd" d="M8.893 1.5c-.183-.31-.52-.5-.887-.5s-.703.19-.886.5L.138 13.499a.98.98 0 0 0 0 1.001c.193.31.53.501.886.501h13.964c.367 0 .704-.19.877-.5a1.03 1.03 0 0 0 .01-1.002L8.893 1.5zm.133 11.497H6.987v-2.003h2.039v2.003zm0-3.004H6.987V5.987h2.039v4.006z"></path></svg></span>Disclaimer</div><div class="admonitionContent_BuS1"><p>The information provided in this post is for educational and informational purposes only. I am not a professional electrician, engineer, or security expert. Any modifications to electrical systems, including doorbells, carry inherent risks, such as damage to property, malfunction, or personal injury. If you choose to follow the steps outlined here, you do so at your own risk. Always take proper safety precautions, consult professionals when necessary, and ensure compliance with local laws and regulations. I cannot be held liable for any consequences resulting from the use or misuse of the information in this post.</p></div></div>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="requirements">Requirements<a href="https://kairos.io/blog/2025/03/18/how-i-automated-my-doorbell-with-kairos-and-you-can-too/#requirements" class="hash-link" aria-label="Direct link to Requirements" title="Direct link to Requirements" translate="no">​</a></h2>
<p>For this setup I used the following hardware</p>
<ul>
<li class="">Honeywell D117 doorbell using the D780 transformer</li>
<li class="">Finder 40.52.8.006.0000 6V AC relay and 95.85.3 relay socket</li>
<li class="">Doorbell cable and male to female jumper cables</li>
<li class="">Raspberry Pi 4B 8G with its power adapter and an SD card and a RJ45 cable to connect it to the internet</li>
</ul>
<p>And on the software side of things all you need is docker, but you can also use other container engine if you have experience building and running images there.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="hardware">Hardware<a href="https://kairos.io/blog/2025/03/18/how-i-automated-my-doorbell-with-kairos-and-you-can-too/#hardware" class="hash-link" aria-label="Direct link to Hardware" title="Direct link to Hardware" translate="no">​</a></h2>
<p>My doorbell is a Honeywell D117, aka Ding Dong (gotta love the name). It’s using the D780 transformer with the following connection (diagram on the left of the picture).</p>
<p><img decoding="async" loading="lazy" alt="Diagram of a Honeywell D117 doorbell with a D780 transformer" src="https://kairos.io/assets/images/424012408-2fbdd893-dba4-496e-9bbc-6450418d5eb4-0d4ad722a24df1d060cb92cc9d4b386a.png" width="549" height="700" class="img_ev3q"></p>
<p>The transformer takes 220V and produces an 8V current</p>
<p><img decoding="async" loading="lazy" alt="Transformer D780" src="https://kairos.io/assets/images/424012979-da048846-16f8-41ca-8673-1467a1028fa3-c90c89e0ec699015934975047017e884.jpeg" width="810" height="968" class="img_ev3q"></p>
<p>We can now use a relay to detect when the circuit is closed. I wasn’t able to find an 8V AC relay, so I tried with a 12V AC and a 6V AC. The 12V one didn't work but the 6V one did. I cannot tell how bad an idea this is so only try this at your own risk. The brand is FINDER and the part number is <code>40.52.8.006.0000</code>, I bought it from <a href="https://www.reichelt.de/de/de/shop/produkt/steckrelais_2x_um_250v_8a_6vac_rm_5_0mm-271335" target="_blank" rel="noopener noreferrer" class="">Reichelt</a> and got it sent to Belgium</p>
<p>Connect <code>A1</code> and <code>A2</code> to <code>0F</code> and <code>T3</code> respectively.</p>
<p><img decoding="async" loading="lazy" alt="Doorbell Wiring" src="https://kairos.io/assets/images/424013401-f1afd596-60ef-4181-92c3-250af52693a3-d2e93dfb0df3e05f25caa854a83f64f6.jpeg" width="768" height="1024" class="img_ev3q"></p>
<p>We will use the always open circuit on the other side of the relay so connect a male to female cable on 11 and 14 which will go to the Raspberry Pi.</p>
<p><img decoding="async" loading="lazy" alt="Relay Wiring" src="https://kairos.io/assets/images/424014404-8aac2983-3208-4792-a14e-713afea7bd0d-86b4902308cc646c229c58074c757f65.jpeg" width="768" height="1024" class="img_ev3q"></p>
<p>I connected it to <a href="https://pinout.xyz/pinout/pin16_gpio23/" target="_blank" rel="noopener noreferrer" class="">GPIO 23</a> and <a href="https://pinout.xyz/pinout/ground" target="_blank" rel="noopener noreferrer" class="">Ground (14)</a></p>
<p><img decoding="async" loading="lazy" alt="RPi Wiring" src="https://kairos.io/assets/images/424014588-c10b4573-dc3d-478c-9853-07abbafaef8c-0b9abf69726caf58fb1cd35b73a0349c.jpeg" width="1024" height="768" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="software">Software<a href="https://kairos.io/blog/2025/03/18/how-i-automated-my-doorbell-with-kairos-and-you-can-too/#software" class="hash-link" aria-label="Direct link to Software" title="Direct link to Software" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="system-image">System Image<a href="https://kairos.io/blog/2025/03/18/how-i-automated-my-doorbell-with-kairos-and-you-can-too/#system-image" class="hash-link" aria-label="Direct link to System Image" title="Direct link to System Image" translate="no">​</a></h3>
<p>Now that all the cabling is done, let’s prepare the software. First I’m going to prepare the image for the SD card. For that I’ll use Kairos because it will make it easier for me to do upgrades in the future and because it’s immutable so I can have my infrastructure as code easily. All I have to do is build a raw image which I can then copy to the SD card.</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">docker</span><span class="token plain"> run </span><span class="token parameter variable" style="color:#36acaa">--rm</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">--privileged</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">-v</span><span class="token plain"> /var/run/docker.sock:/var/run/docker.sock </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">-v</span><span class="token plain"> </span><span class="token environment constant" style="color:#36acaa">$PWD</span><span class="token plain">/build/:/output </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  quay.io/kairos/auroraboot:latest </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">--debug</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">--set</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"disable_http_server=true"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">--set</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"disable_netboot=true"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">--set</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"container_image=quay.io/kairos/opensuse:leap-15.6-standard-arm64-rpi4-v3.3.1-k3sv1.32.1-k3s1"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">--set</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"state_dir=/output"</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">--set</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"disk.raw=true"</span><br></div></code></pre></div></div>
<p>There’s a lot in this command, which you can learn in the Kairos documentation but the one important thing to know is that I’m consuming the Kairos image that is specially built for Raspberry Pi 4 and that it contains the K3s Kubernetes distribution in it so I can deploy my script via Kubernetes and leave the base image unchanged.</p>
<p>If everything is successful you should get the image <code>build/kairos-opensuse-leap-15.6-standard-arm64-rpi4-v3.3.1-k3s1.32.1.raw</code> so let’s copy it into the SD card, I’m on Linux so I can run the following</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">sudo</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">dd</span><span class="token plain"> </span><span class="token assign-left variable" style="color:#36acaa">if</span><span class="token operator" style="color:#393A34">=</span><span class="token plain">./build/kairos-opensuse-leap-15.6-standard-arm64-rpi4-v3.3.1-k3s1.32.1.raw </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token assign-left variable" style="color:#36acaa">of</span><span class="token operator" style="color:#393A34">=</span><span class="token plain">/dev/mmblk0 </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token assign-left variable" style="color:#36acaa">oflag</span><span class="token operator" style="color:#393A34">=</span><span class="token plain">sync </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token assign-left variable" style="color:#36acaa">status</span><span class="token operator" style="color:#393A34">=</span><span class="token plain">progress </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token assign-left variable" style="color:#36acaa">bs</span><span class="token operator" style="color:#393A34">=</span><span class="token plain">10MB</span><br></div></code></pre></div></div>
<p>Once it finishes copying, you can insert it on the Raspberry Pi and boot it. It will do an initial boot to setup the system and reboot on its own. In the meantime let’s prepare the software we are going to deploy.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="telegram-bot">Telegram Bot<a href="https://kairos.io/blog/2025/03/18/how-i-automated-my-doorbell-with-kairos-and-you-can-too/#telegram-bot" class="hash-link" aria-label="Direct link to Telegram Bot" title="Direct link to Telegram Bot" translate="no">​</a></h3>
<p>I will be using a telegram bot to send the messages. This way anyone in the family can subscribe to it and mute it if they want. If you prefer a different solution just adapt the Python script in the next section.</p>
<ol>
<li class="">Open Telegram and search for BotFather.</li>
<li class="">Type /newbot and follow the steps to create a bot.</li>
<li class="">Copy the API token that BotFather gives you.</li>
<li class="">Interact with your bot by sending any message</li>
<li class="">Extract the Chat ID by going to a browser using the api token you got in one of the previous steps <a href="https://api.telegram.org/botYOUR_API_TOKEN/getUpdates" target="_blank" rel="noopener noreferrer" class="">https://api.telegram.org/botYOUR_API_TOKEN/getUpdates</a></li>
</ol>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="python-script">Python Script<a href="https://kairos.io/blog/2025/03/18/how-i-automated-my-doorbell-with-kairos-and-you-can-too/#python-script" class="hash-link" aria-label="Direct link to Python Script" title="Direct link to Python Script" translate="no">​</a></h3>
<p>This script will detect when there’s a signal in GPIO 23, write a log and send a Telegram message</p>
<div class="language-python codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-python codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> os</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> lgpio </span><span class="token keyword" style="color:#00009f">as</span><span class="token plain"> GPIO</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> time</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> requests</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> datetime </span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> datetime</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># Read environment variables</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">BOT_TOKEN </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> os</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">environ</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">get</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"TELEGRAM_BOT_TOKEN"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">CHAT_ID </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> os</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">environ</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">get</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"TELEGRAM_CHAT_ID"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># GPIO Setup</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">GPIO_PIN </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token number" style="color:#36acaa">23</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">h </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> GPIO</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">gpiochip_open</span><span class="token punctuation" style="color:#393A34">(</span><span class="token number" style="color:#36acaa">0</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">GPIO</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">gpio_claim_input</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">h</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> GPIO_PIN</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> GPIO</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">SET_PULL_UP</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">def</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">send_telegram_message</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">message</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token keyword" style="color:#00009f">if</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">not</span><span class="token plain"> BOT_TOKEN </span><span class="token keyword" style="color:#00009f">or</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">not</span><span class="token plain"> CHAT_ID</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token keyword" style="color:#00009f">print</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"❌ Error: Missing environment variables for Telegram bot."</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token keyword" style="color:#00009f">return</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    url </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token string-interpolation string" style="color:#e3116c">f"&lt;https://api.telegram.org/bot</span><span class="token string-interpolation interpolation punctuation" style="color:#393A34">{</span><span class="token string-interpolation interpolation">BOT_TOKEN</span><span class="token string-interpolation interpolation punctuation" style="color:#393A34">}</span><span class="token string-interpolation string" style="color:#e3116c">/sendMessage&gt;"</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    payload </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token string" style="color:#e3116c">"chat_id"</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> CHAT_ID</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"text"</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> message</span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    requests</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">post</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">url</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> json</span><span class="token operator" style="color:#393A34">=</span><span class="token plain">payload</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">print</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"🚀 Doorbell monitor started..."</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">while</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">True</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token keyword" style="color:#00009f">if</span><span class="token plain"> GPIO</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">gpio_read</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">h</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> GPIO_PIN</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">==</span><span class="token plain"> </span><span class="token number" style="color:#36acaa">0</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic"># Button pressed</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        timestamp </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> datetime</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">now</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">strftime</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">"%Y-%m-%d %H:%M:%S"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        message </span><span class="token operator" style="color:#393A34">=</span><span class="token plain"> </span><span class="token string-interpolation string" style="color:#e3116c">f"🚪 Doorbell pressed at </span><span class="token string-interpolation interpolation punctuation" style="color:#393A34">{</span><span class="token string-interpolation interpolation">timestamp</span><span class="token string-interpolation interpolation punctuation" style="color:#393A34">}</span><span class="token string-interpolation string" style="color:#e3116c">!"</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token keyword" style="color:#00009f">print</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string-interpolation string" style="color:#e3116c">f"[</span><span class="token string-interpolation interpolation punctuation" style="color:#393A34">{</span><span class="token string-interpolation interpolation">timestamp</span><span class="token string-interpolation interpolation punctuation" style="color:#393A34">}</span><span class="token string-interpolation string" style="color:#e3116c">] 🔔 </span><span class="token string-interpolation interpolation punctuation" style="color:#393A34">{</span><span class="token string-interpolation interpolation">message</span><span class="token string-interpolation interpolation punctuation" style="color:#393A34">}</span><span class="token string-interpolation string" style="color:#e3116c">"</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        send_telegram_message</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">message</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        time</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">sleep</span><span class="token punctuation" style="color:#393A34">(</span><span class="token number" style="color:#36acaa">2</span><span class="token punctuation" style="color:#393A34">)</span><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic"># Avoid spamming messages</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    time</span><span class="token punctuation" style="color:#393A34">.</span><span class="token plain">sleep</span><span class="token punctuation" style="color:#393A34">(</span><span class="token number" style="color:#36acaa">0.1</span><span class="token punctuation" style="color:#393A34">)</span><br></div></code></pre></div></div>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="dockerfile">Dockerfile<a href="https://kairos.io/blog/2025/03/18/how-i-automated-my-doorbell-with-kairos-and-you-can-too/#dockerfile" class="hash-link" aria-label="Direct link to Dockerfile" title="Direct link to Dockerfile" translate="no">​</a></h3>
<p>We won’t run the script directly on the Raspberry Pi, it will be running in a Docker container. This is very useful when having the underlying system be immutable because I can still iterate without having to rebuild and burn a new SD card and restart the system. Instead all I have to do is install the packages I need in this container and run it in privilege mode. This of course can open some security risks, but again, this is just for learning purposes and for fun.</p>
<div class="language-dockerfile codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-dockerfile codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token comment" style="color:#999988;font-style:italic"># Use a lightweight Python base image for Raspberry Pi (ARM)</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token instruction keyword" style="color:#00009f">FROM</span><span class="token instruction"> python:3.9-slim</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># Install system dependencies</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token instruction keyword" style="color:#00009f">RUN</span><span class="token instruction"> apt update &amp;&amp; apt install -y python3-dev gcc</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token instruction keyword" style="color:#00009f">RUN</span><span class="token instruction"> pip install lgpio requests</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># Set the working directory inside the container</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token instruction keyword" style="color:#00009f">WORKDIR</span><span class="token instruction"> /app</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># Copy the Python script into the container</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token instruction keyword" style="color:#00009f">COPY</span><span class="token instruction"> doorbell.py /app/doorbell.py</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token comment" style="color:#999988;font-style:italic"># Set the script to run on startup</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token instruction keyword" style="color:#00009f">CMD</span><span class="token instruction"> [</span><span class="token instruction string" style="color:#e3116c">"python3"</span><span class="token instruction">, </span><span class="token instruction string" style="color:#e3116c">"/app/doorbell.py"</span><span class="token instruction">]</span><br></div></code></pre></div></div>
<p>Since the image is going to be running on the Raspberry Pi but I’m going to build it on an AMD platform, then I need to cross-compile. Use any tag you prefer, just keep in mind it is the same tag you have to use in the deployment in the next section</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">docker</span><span class="token plain"> buildx build </span><span class="token parameter variable" style="color:#36acaa">--platform</span><span class="token operator" style="color:#393A34">=</span><span class="token plain">linux/arm64 </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token parameter variable" style="color:#36acaa">-t</span><span class="token plain"> quay.io/mauromorales/doorbell:telegram-v1 </span><span class="token punctuation" style="color:#393A34">\</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token builtin class-name">.</span><br></div></code></pre></div></div>
<p>And publish it to a repository, I’m using Quay but you can use any repo you prefer</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">docker</span><span class="token plain"> push quay.io/mauromorales/doorbell:telegram-v1</span><br></div></code></pre></div></div>
<p>Yes that image is public and will remain static, but I’d recommend you build your own instead of using mine because at any moment I might decide to remove it.</p>
<h3 class="anchor anchorTargetStickyNavbar_Vzrq" id="kubernetes">Kubernetes<a href="https://kairos.io/blog/2025/03/18/how-i-automated-my-doorbell-with-kairos-and-you-can-too/#kubernetes" class="hash-link" aria-label="Direct link to Kubernetes" title="Direct link to Kubernetes" translate="no">​</a></h3>
<p>Last piece of the puzzle is the Kubernetes deployment. Let’s log into our Kairos system with user <code>kairos</code> and password <code>kairos</code></p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token function" style="color:#d73a49">ssh</span><span class="token plain"> kairos@IP</span><br></div></code></pre></div></div>
<p>Switch to root</p>
<div class="language-text codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-text codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token plain">sudo -i</span><br></div></code></pre></div></div>
<p>We want to create some secrets and pass them as environment variables in the container. Take the telegram bot token and chat id and encode them. For example if my Chat ID is <code>1234567890</code> then I’d do as follows:</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token builtin class-name">echo</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">-n</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"1234567890"</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">|</span><span class="token plain"> base64</span><br></div></code></pre></div></div>
<p>do the same with the bot token, e.g. if my bot token was <code>999999999:FooooooBaaaaaaaaR</code> then I’d do</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token builtin class-name">echo</span><span class="token plain"> </span><span class="token parameter variable" style="color:#36acaa">-n</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"999999999:FooooooBaaaaaaaaR"</span><span class="token plain"> </span><span class="token operator" style="color:#393A34">|</span><span class="token plain"> base64</span><br></div></code></pre></div></div>
<p>and copy them in a file called <code>telegram-secrets.yaml</code> and add the following content (remember to replace with your actual encoded values). Yes Kairos is immutable in some areas but the home directory is writable.</p>
<div class="language-yaml codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-yaml codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token key atrule" style="color:#00a4db">apiVersion</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> v1</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">kind</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> Secret</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">metadata</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">name</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> telegram</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">secrets</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">type</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> Opaque</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">data</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">bot_token</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> OTk5OTk5OTk5OkZvb29vb29CYWFhYWFhYWFS</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">chat_id</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> MTIzNDU2Nzg5MA==</span><br></div></code></pre></div></div>
<p>Save the file and apply it</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token plain">kubectl apply </span><span class="token parameter variable" style="color:#36acaa">-f</span><span class="token plain"> telegram-secret.yaml</span><br></div></code></pre></div></div>
<p>Now we create a <code>deployment.yaml</code> file to connect everything together</p>
<div class="language-yaml codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-yaml codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token key atrule" style="color:#00a4db">apiVersion</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> apps/v1</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">kind</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> Deployment</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">metadata</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">name</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> rpi</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">doorbell</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token key atrule" style="color:#00a4db">spec</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">replicas</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> </span><span class="token number" style="color:#36acaa">1</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">selector</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token key atrule" style="color:#00a4db">matchLabels</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token key atrule" style="color:#00a4db">app</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> doorbell</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token key atrule" style="color:#00a4db">template</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token key atrule" style="color:#00a4db">metadata</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token key atrule" style="color:#00a4db">labels</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token key atrule" style="color:#00a4db">app</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> doorbell</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token key atrule" style="color:#00a4db">spec</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token key atrule" style="color:#00a4db">containers</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain"> </span><span class="token key atrule" style="color:#00a4db">name</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> doorbell</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token key atrule" style="color:#00a4db">image</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> quay.io/mauromorales/doorbell</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain">telegram</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">v1</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token key atrule" style="color:#00a4db">imagePullPolicy</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> Always   </span><span class="token comment" style="color:#999988;font-style:italic"># Forces Kubernetes to always pull the latest image</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token key atrule" style="color:#00a4db">securityContext</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          </span><span class="token key atrule" style="color:#00a4db">privileged</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean important" style="color:#36acaa">true</span><span class="token plain">  </span><span class="token comment" style="color:#999988;font-style:italic"># Allows access to GPIO hardware</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token key atrule" style="color:#00a4db">resources</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          </span><span class="token key atrule" style="color:#00a4db">limits</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">            </span><span class="token key atrule" style="color:#00a4db">memory</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"128Mi"</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">            </span><span class="token key atrule" style="color:#00a4db">cpu</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">"100m"</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">        </span><span class="token key atrule" style="color:#00a4db">env</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          </span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain"> </span><span class="token key atrule" style="color:#00a4db">name</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> TELEGRAM_BOT_TOKEN</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">            </span><span class="token key atrule" style="color:#00a4db">valueFrom</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">              </span><span class="token key atrule" style="color:#00a4db">secretKeyRef</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">                </span><span class="token key atrule" style="color:#00a4db">name</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> telegram</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">secrets</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">                </span><span class="token key atrule" style="color:#00a4db">key</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> bot_token</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">          </span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain"> </span><span class="token key atrule" style="color:#00a4db">name</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> TELEGRAM_CHAT_ID</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">            </span><span class="token key atrule" style="color:#00a4db">valueFrom</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">              </span><span class="token key atrule" style="color:#00a4db">secretKeyRef</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">                </span><span class="token key atrule" style="color:#00a4db">name</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> telegram</span><span class="token punctuation" style="color:#393A34">-</span><span class="token plain">secrets</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">                </span><span class="token key atrule" style="color:#00a4db">key</span><span class="token punctuation" style="color:#393A34">:</span><span class="token plain"> chat_id</span><br></div></code></pre></div></div>
<p>And apply it</p>
<div class="language-bash codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-bash codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token plain">kubectl apply </span><span class="token parameter variable" style="color:#36acaa">-f</span><span class="token plain"> deployment.yaml</span><br></div></code></pre></div></div>
<p>If everything went as expected, you should see your pod running</p>
<div class="language-text codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-text codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token plain">localhost:~ # kubectl get pods</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">NAME                            READY   STATUS    RESTARTS   AGE</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">rpi-doorbell-67c78c5969-s6pw8   1/1     Running   0          20h</span><br></div></code></pre></div></div>
<p>And you can get logs from that pod tracking every time someone pressed your doorbell in addition to sending the Telegram message</p>
<div class="language-text codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_QJqH"><pre tabindex="0" class="prism-code language-text codeBlock_bY9V thin-scrollbar" style="color:#393A34;background-color:#f6f8fa"><code class="codeBlockLines_e6Vv"><div class="token-line" style="color:#393A34"><span class="token plain">localhost:~ # kubectl logs rpi-doorbell-67c78c5969-s6pw8</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">🚀 Doorbell monitor started...</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">[2025-03-05 13:51:34] 🔔 🚪 Doorbell pressed at 2025-03-05 13:51:34!</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">[2025-03-05 15:41:25] 🔔 🚪 Doorbell pressed at 2025-03-05 15:41:25!</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">[2025-03-05 15:42:13] 🔔 🚪 Doorbell pressed at 2025-03-05 15:42:13!</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">[2025-03-05 18:28:26] 🔔 🚪 Doorbell pressed at 2025-03-05 18:28:26!</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">[2025-03-06 09:59:18] 🔔 🚪 Doorbell pressed at 2025-03-06 09:59:18!</span><br></div></code></pre></div></div>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="conclusion">Conclusion<a href="https://kairos.io/blog/2025/03/18/how-i-automated-my-doorbell-with-kairos-and-you-can-too/#conclusion" class="hash-link" aria-label="Direct link to Conclusion" title="Direct link to Conclusion" translate="no">​</a></h2>
<p>With this setup me and my partner can subscribe to the Telegram Bot and get notifications to our phones. I can also mute the bot if I’m in a meeting and don’t want to be disturbed. I could extend the system to not notify at certain hours of the day but still keep logs. If I’m not happy with Telegram then I can connect it to a different system. Whenever there’s a new version of Kairos I can upgrade the system remotely via the command line or through Kubernetes. If you have a similar setup but don’t want to buy a smart doorbell just yet, I can only recommend this setup.</p>
<p><img decoding="async" loading="lazy" alt="Telegram Bot" src="https://kairos.io/assets/images/424011822-c86d85e4-86b5-465d-bf1a-83a8850916bc-2e83732522a8de7f1618c60511b9918e.jpeg" width="602" height="1304" class="img_ev3q"></p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Kairos Joins the CNCF as a Sandbox Project]]></title>
            <link>https://kairos.io/blog/2024/10/08/kairos-joins-the-cncf-as-a-sandbox-project/</link>
            <guid>https://kairos.io/blog/2024/10/08/kairos-joins-the-cncf-as-a-sandbox-project/</guid>
            <pubDate>Tue, 08 Oct 2024 00:00:00 GMT</pubDate>
            <description><![CDATA[We’re thrilled to announce that since April 2024, Kairos has been officially part of the Cloud Native Computing Foundation (CNCF) as a Sandbox Project. This marks an important milestone for Kairos and, more importantly, for our entire community of users and contributors.]]></description>
            <content:encoded><![CDATA[<p>We’re thrilled to announce that since April 2024, Kairos has been officially part of the Cloud Native Computing Foundation (CNCF) as a Sandbox Project. This marks an important milestone for Kairos and, more importantly, for our entire community of users and contributors.</p>
<p>You might be wondering - what does being part of the CNCF mean for you? The CNCF is known for backing the most innovative, reliable, and secure projects in the cloud-native space, and having their support brings a number of crucial benefits. Let’s dive into why this matters.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="stability-and-long-term-support">Stability and Long-Term Support<a href="https://kairos.io/blog/2024/10/08/kairos-joins-the-cncf-as-a-sandbox-project/#stability-and-long-term-support" class="hash-link" aria-label="Direct link to Stability and Long-Term Support" title="Direct link to Stability and Long-Term Support" translate="no">​</a></h2>
<p>First and foremost, being part of the CNCF ensures that Kairos is built to last. The CNCF provides a stable and structured environment that safeguards against a project disappearing overnight, something that can be a concern for open-source users. With CNCF backing us, you can rest assured that Kairos is part of a thriving, open-source ecosystem with the resources and backing to stay sustainable for the long term.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="higher-standards-and-best-practices">Higher Standards and Best Practices<a href="https://kairos.io/blog/2024/10/08/kairos-joins-the-cncf-as-a-sandbox-project/#higher-standards-and-best-practices" class="hash-link" aria-label="Direct link to Higher Standards and Best Practices" title="Direct link to Higher Standards and Best Practices" translate="no">​</a></h2>
<p>We've been quiet about this milestone until now because the CNCF onboarding process is rigorous, and we wanted to make sure we did it right. This onboarding process wasn’t just about paperwork—it pushed us to adopt even higher levels of best practices. You can see some of the measures we've adopted as part of this effort <a href="https://www.bestpractices.dev/en/projects/9100" target="_blank" rel="noopener noreferrer" class="">here</a>. These improvements have been critical in refining Kairos, and we've emerged from the onboarding process more secure, more reliable, and better aligned with industry standards.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="growing-and-collaborating-with-the-cloud-native-community">Growing and Collaborating with the Cloud Native Community<a href="https://kairos.io/blog/2024/10/08/kairos-joins-the-cncf-as-a-sandbox-project/#growing-and-collaborating-with-the-cloud-native-community" class="hash-link" aria-label="Direct link to Growing and Collaborating with the Cloud Native Community" title="Direct link to Growing and Collaborating with the Cloud Native Community" translate="no">​</a></h2>
<p>Joining the CNCF has opened many doors for us to connect with other projects and communities. This past year, we've had the privilege of participating in KubeCon + CloudNativeCon in Hong Kong as part of the Project Pavilion, where we had a booth to engage with users and fellow contributors. We’ll be doing the same at KubeCon North America, and we’d love to see you there!</p>
<p>Come visit us on Wednesday, November 13, from 10:30 am to 3:15 pm at the Project Pavilion area of KubeCon North America. Through these events, we've had the chance to collaborate with other CNCF project maintainers, share knowledge, and learn from one another. The spirit of open collaboration is at the heart of everything we do, and we’ve gained valuable insights that are helping us make Kairos even better for you, our users.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="improved-ci-with-arm-support">Improved CI with ARM Support<a href="https://kairos.io/blog/2024/10/08/kairos-joins-the-cncf-as-a-sandbox-project/#improved-ci-with-arm-support" class="hash-link" aria-label="Direct link to Improved CI with ARM Support" title="Direct link to Improved CI with ARM Support" translate="no">​</a></h2>
<p>Another benefit of being part of the CNCF is access to resources we didn't have before. Thanks to the CNCF, we now have ARM machines integrated into our CI pipelines, allowing us to test and build more efficiently. This not only speeds up our development process but also ensures Kairos runs smoothly on a wider range of hardware platforms, enhancing performance and broadening the scope of where you can use it.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="a-community-effort">A Community Effort<a href="https://kairos.io/blog/2024/10/08/kairos-joins-the-cncf-as-a-sandbox-project/#a-community-effort" class="hash-link" aria-label="Direct link to A Community Effort" title="Direct link to A Community Effort" translate="no">​</a></h2>
<p>Finally, we want to emphasize that none of this would have been possible without you—our community. Your support, feedback, and contributions are what drive Kairos forward. Whether it’s through submitting pull requests, reporting issues, or simply sharing your experiences, you have been an integral part of our journey. We are grateful to have such a passionate and engaged community that keeps us motivated and moving in the right direction.</p>
<p>As we continue to grow within the CNCF and the cloud-native space, we’re excited about the opportunities that lie ahead. We remain committed to building Kairos in a way that benefits all of us, and we can’t wait to share more with you in the future.</p>
<p>See you at KubeCon North America, and thank you for being with us every step of the way!</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Hacktoberfest 2024]]></title>
            <link>https://kairos.io/blog/2024/10/07/hacktoberfest-2024/</link>
            <guid>https://kairos.io/blog/2024/10/07/hacktoberfest-2024/</guid>
            <pubDate>Mon, 07 Oct 2024 00:00:00 GMT</pubDate>
            <description><![CDATA[Kairos' Hacktoberfest]]></description>
            <content:encoded><![CDATA[<p><img decoding="async" loading="lazy" src="https://github.com/user-attachments/assets/e79ca5ed-97fe-4eaf-b31c-1fd01ff457f0" alt="Kairos' Hacktoberfest" class="img_ev3q"></p>
<p>I can't believe it's already October. I've been so busy following up on different events where we've brought some of the Kairos love that I forgot about <a href="https://hacktoberfest.com/" target="_blank" rel="noopener noreferrer" class="">Hacktoberfest</a>. Thankfully, the month isn't over so let's get our hands dirty!</p>
<p>Like <a href="https://kairos.io/blog/2023/09/26/hacktoberfest-2023/" target="_blank" rel="noopener noreferrer" class="">last year</a> Kairos is taking part in this event. This means that you can open PRs in any of our repositories, and we'll make sure to tag them correctly so they count towards your progress (please contact us if this is not the case).</p>
<p>If you'd like to participate, start by looking at the tickets with the <a href="https://github.com/kairos-io/kairos/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest" target="_blank" rel="noopener noreferrer" class="">hacktoberfest label</a>, but you can hack on any other ticket and we'll be happy to add the tag for you.</p>
<p>This year, we will offer Kairos t-shirts and stickers to the first 10 contributions. So don't wait too long to participate.</p>
<p>Disclaimer: Only accepted PRs will count and Kairos is just an open-source project and we cannot guarantee that we can send swag anywhere in the world.</p>]]></content:encoded>
            <category>Kairos</category>
        </item>
        <item>
            <title><![CDATA[Enhancing Kairos Documentation with a Customizable Flavor Menu]]></title>
            <link>https://kairos.io/blog/2024/08/14/enhancing-kairos-documentation-with-a-customizable-flavor-menu/</link>
            <guid>https://kairos.io/blog/2024/08/14/enhancing-kairos-documentation-with-a-customizable-flavor-menu/</guid>
            <pubDate>Wed, 14 Aug 2024 00:00:00 GMT</pubDate>
            <description><![CDATA[Discover how our new customizable flavor menu in Kairos documentation streamlines your experience by allowing you to select your preferred Linux distribution.]]></description>
            <content:encoded><![CDATA[<p>Kairos is versatile, supporting various Linux distributions such as openSUSE Leap, Ubuntu 24.04, and <a class="" href="https://kairos.io/docs/reference/image_matrix/">more</a>. Our primary objective is to empower users to continue working with their preferred Linux distribution seamlessly. However, our previous documentation fell short of this goal. The scripts were tied to a default image, which often led to issues for users who preferred a different flavor.</p>
<p>During our <a class="" href="https://kairos.io/blog/2024/08/13/our-first-hackweek/">first Hackweek</a>, we took a significant step forward by updating our documentation to allow users to select their preferred flavor, thereby enhancing the overall experience.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-does-it-work">How does it work?<a href="https://kairos.io/blog/2024/08/14/enhancing-kairos-documentation-with-a-customizable-flavor-menu/#how-does-it-work" class="hash-link" aria-label="Direct link to How does it work?" title="Direct link to How does it work?" translate="no">​</a></h2>
<p>To select your preferred flavor, simply use the drop-down menu at the top of the navigation bar on our website. Your selection is saved locally, meaning that if you access the documentation from a different browser or device, you’ll need to reselect your flavor.</p>
<p>Selecting your preferred flavor will automatically update the scripts displayed on the page. If an example is specific to a certain flavor, such as the installation on <a class="" href="https://kairos.io/docs/installation/nvidia_agx_orin/">Nvidia AGX Orin</a>, you will see a warning at the top of the page, and the scripts will not switch to your selected flavor. When only a subset of flavors is available, and your preferred one is not among them, a warning message will appear above the script, informing you of the available flavors. The script will default to the first available option.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="give-us-feedback">Give us feedback!<a href="https://kairos.io/blog/2024/08/14/enhancing-kairos-documentation-with-a-customizable-flavor-menu/#give-us-feedback" class="hash-link" aria-label="Direct link to Give us feedback!" title="Direct link to Give us feedback!" translate="no">​</a></h2>
<p>We hope this new feature enhances your experience with our documentation. If you have any feedback or suggestions, please don’t hesitate to reach out to us on the <a href="https://cloud-native.slack.com/archives/C0707M8UEU8" target="_blank" rel="noopener noreferrer" class="">CNCF Slack channel</a></p>]]></content:encoded>
            <category>Kairos</category>
        </item>
    </channel>
</rss>