<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>K8s on johanneskueber.com</title><link>https://johanneskueber.com/tags/k8s/</link><description>Recent content in K8s on johanneskueber.com</description><generator>Hugo</generator><language>en_US</language><lastBuildDate>Sat, 11 Oct 2025 21:06:26 +0000</lastBuildDate><atom:link href="https://johanneskueber.com/tags/k8s/index.xml" rel="self" type="application/rss+xml"/><item><title>Intel iGPU passthrough with Proxmox and Talos</title><link>https://johanneskueber.com/posts/2025-10-11-proxmox-passthrough-talos/</link><pubDate>Sat, 11 Oct 2025 21:06:26 +0000</pubDate><guid>https://johanneskueber.com/posts/2025-10-11-proxmox-passthrough-talos/</guid><description>&lt;h2 id="igpu-passthrough-with-proxmox-and-talos"&gt;iGPU Passthrough with Proxmox and Talos&lt;/h2&gt;
&lt;p&gt;To use the GPU of the host system in K8s, it needs to be made aware of its existence. As I use VMs in Proxmox to run my Talos Cluster, there is an additional step to consider: passthrough of the hardware into the VM. The idea is the following:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Disable usage of GPU on the Proxmox Host - done via IOMMU and VFIO&lt;/li&gt;
&lt;li&gt;Passthrough of the GPU into a Talos Worker Node - done via hostpci&lt;/li&gt;
&lt;li&gt;Activation of GPU drivers in Talos - done via talhelper&lt;/li&gt;
&lt;li&gt;GPU management in the cluster - done via Intel GPU Plugin&lt;/li&gt;
&lt;li&gt;Usage of GPU in a deployment - by requesting the resource&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;There are quite some steps and all of them are specific to your environment. Different host system? Different steps. Different Cluster Software? You need to adept. Different GPU? You need other drivers and management. So please look out for the pitfalls and only copy and paste if you run proxmox with talos and have an Intel iGPU.&lt;/p&gt;</description></item><item><title>Use Longhorn with Talos 1.10 and userVolumes</title><link>https://johanneskueber.com/posts/2025-06-17-longhorn-uservolumes-talos/</link><pubDate>Tue, 17 Jun 2025 07:06:26 +0000</pubDate><guid>https://johanneskueber.com/posts/2025-06-17-longhorn-uservolumes-talos/</guid><description>&lt;p&gt;When building a cluster, especially in a homelab, local storage is needed for application data. Especially for databases fast read and write is required. Offloading the workload to a NAS most of the time is slower. The solution I use is to provision on-node storage with &lt;a href="https://longhorn.io/"&gt;Longhorn&lt;/a&gt;. Longhorn acts as a CSI and offers on-node storage, replication, backups and more.&lt;/p&gt;
&lt;p&gt;As I am currently building a Talos cluster I need to integrate the longhorn CSI into the setup. This is not as straigt forward as with K3s oder K8s, as Talos has tighter security constraints and also needs additional plugins to handle SCSI - the underlying file system protocol used by longhorn. On top I am using &lt;a href="https://budimanjojo.github.io/talhelper/latest/"&gt;Talhelper&lt;/a&gt; to allow a GitOps style usage of talosctl. The main advantage is the encryption of secrets used by talos config files with &lt;a href="https://github.com/getsops/sops"&gt;SOPS&lt;/a&gt; - something that I already use for Tofu and fluxCD.&lt;/p&gt;</description></item></channel></rss>