<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bjørn Kristian Strand on Home</title><link>https://blog.bkristian.net/authors/bj%C3%B8rn-kristian-strand/</link><description>Recent content in Bjørn Kristian Strand on Home</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 06 Jul 2026 16:12:52 +0200</lastBuildDate><atom:link href="https://blog.bkristian.net/authors/bj%C3%B8rn-kristian-strand/index.xml" rel="self" type="application/rss+xml"/><item><title>Bootstrapping my new bare-metal kubernetes cluster with talos</title><link>https://blog.bkristian.net/posts/bootstrapping-talos/</link><pubDate>Mon, 06 Jul 2026 16:12:52 +0200</pubDate><guid>https://blog.bkristian.net/posts/bootstrapping-talos/</guid><description>&lt;p&gt;After using &lt;a href="https://www.proxmox.com/en/" class="external-link" target="_blank" rel="noopener"&gt;proxmox&lt;/a&gt; on my homelab for a few years and virtualizing my workloads (both kubernetes and regular VMs), i decided that i wanted to 1) remove the virtualization overhead as i was just wasting resources on a virtualization-layer i did not want to maintain, and 2) make the switch from &lt;a href="https://k3s.io/" class="external-link" target="_blank" rel="noopener"&gt;k3s&lt;/a&gt; to &lt;a href="https://www.siderolabs.com/talos-linux" class="external-link" target="_blank" rel="noopener"&gt;Talos&lt;/a&gt; for my kubernetes clusters (calling it a &amp;ldquo;cluster&amp;rdquo; is a stretch as i currently just have one node).&lt;/p&gt;
&lt;p&gt;K3s is a great technology for running kubernetes with a low footprint, but for the same reason i wanted to move away from proxmox, i wanted to move away from k3s because i really do not care about maintaining the OS of my kubernetes node(s). Granted, there is a certain level of &amp;ldquo;OS-management&amp;rdquo; you have to do on Talos aswell, but the scope is considerably smaller and is reasonably easy to perform using &lt;code&gt;talosctl&lt;/code&gt; instead of spending a lot of time writing ansible-playbooks.&lt;/p&gt;</description></item></channel></rss>