<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>homelab</title><link>https://docs.magelssen.io/</link><description>Recent content on homelab</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.magelssen.io/index.xml" rel="self" type="application/rss+xml"/><item><title/><link>https://docs.magelssen.io/architecture/hardware/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/architecture/hardware/</guid><description>&lt;h1 id="hardware"&gt;Hardware&lt;a class="anchor" href="#hardware" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="machines"&gt;Machines&lt;a class="anchor" href="#machines" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Machine&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Hostname&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Runs&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Specs&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Lenovo ThinkCentre M720q&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;lenovo1&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Kubernetes control plane, also runs workloads&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;6 cores, 8 GB RAM, ~100 GB disk&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Lenovo ThinkCentre M720q&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;lenovo2&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Kubernetes worker&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;6 cores, 8 GB RAM, ~200 GB disk&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Raspberry Pi 5&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;pi5&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Kubernetes worker (arm64)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;4 cores, 8 GB RAM, ~480 GB disk&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Self-built PC (MSI B250M BAZOOKA)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;pve&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Proxmox VE: TrueNAS SCALE in a VM, and LXCs for the services outside Kubernetes&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Intel Core i5-7400 (4 cores), 40 GB DDR4-2133 (2× 16 GB + 2× 4 GB), 1 GbE, GeForce GTX 1060 3GB&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;p&gt;Node settings for the Kubernetes nodes: &lt;a href="https://docs.magelssen.io/cluster/nodes/"&gt;nodes&lt;/a&gt;.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/architecture/network/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/architecture/network/</guid><description>&lt;h1 id="network"&gt;Network&lt;a class="anchor" href="#network" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;TP-Link Omada, managed from the Omada controller (a TrueNAS app).&lt;/p&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Device&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Model&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Role&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Router&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;TP-Link ER7206&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Gateway and routing between the VLANs&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Switch&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;TP-Link SG2210MP&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;8 gigabit PoE+ ports and 2 SFP slots, VLAN trunks to the hosts&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Access point&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;TP-Link EAP653&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Wi-Fi 6&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;h2 id="vlans"&gt;VLANs&lt;a class="anchor" href="#vlans" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The network is split into VLANs by purpose:&lt;/p&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;VLAN&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Name&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Purpose&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;10&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Core&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Network management and core services&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;20&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Servers&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Proxmox, NAS and services outside Kubernetes&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;30&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Kubernetes&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Cluster nodes and MetalLB load balancer IPs&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;42&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Trusted clients&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Personal devices on Wi-Fi&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;90&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Guests&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Guest Wi-Fi, isolated&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;107&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;IoT&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Smart home devices&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;</description></item><item><title/><link>https://docs.magelssen.io/architecture/storage/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/architecture/storage/</guid><description>&lt;h1 id="storage"&gt;Storage&lt;a class="anchor" href="#storage" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;All data lives on TrueNAS SCALE (a VM on Proxmox) in one pool, &lt;code&gt;Firelink&lt;/code&gt;: three disks&#10;in RAIDZ1, about 7.2 TiB usable. The layout was cleaned up in October 2026, before&#10;backups were set up.&lt;/p&gt;&#10;&lt;h2 id="rule-one-top-level-dataset-per-kind-of-data"&gt;Rule: one top-level dataset per kind of data&lt;a class="anchor" href="#rule-one-top-level-dataset-per-kind-of-data" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Snapshots, retention, quotas and replication are set per dataset in ZFS. So each&#10;top-level dataset holds one kind of data with one backup policy, and anything below it&#10;inherits that policy. Dark Souls names at the top level, plain names below.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/architecture/technology/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/architecture/technology/</guid><description>&lt;h1 id="technology-choices"&gt;Technology choices&lt;a class="anchor" href="#technology-choices" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;What is used, and why in a sentence or two. The larger choices, with the options that were&#10;rejected, are written down as &lt;a href="https://docs.magelssen.io/decisions/"&gt;decision records&lt;/a&gt;.&lt;/p&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Technology&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Why&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Proxmox VE&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Runs the NAS and the services that are not in Kubernetes yet, separate from the cluster. A full hypervisor with LXCs, backups and an API, with TrueNAS in a VM (&lt;a href="https://docs.magelssen.io/decisions/0002-truenas-as-a-vm-on-proxmox/"&gt;ADR 0002&lt;/a&gt;).&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Bare-metal nodes&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Keeps the NAS, the hypervisor and the cluster on separate machines, so one can be rebuilt without touching the others (&lt;a href="https://docs.magelssen.io/decisions/0001-bare-metal-kubernetes-nodes/"&gt;ADR 0001&lt;/a&gt;).&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;kubeadm&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Upstream Kubernetes with no abstractions on top, which is good practice for the Kubernetes certifications. The cluster started on v1.33 and has been upgraded to v1.36 by hand.&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Flannel&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Simple CNI that just works. The trade-off is no NetworkPolicy support, which I may revisit.&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Flux&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Pull-based GitOps: the cluster pulls from Git, so nothing outside needs access to the cluster. No GUI, which forces me to understand Kubernetes properly. It is also what I use at work (&lt;a href="https://docs.magelssen.io/decisions/0003-flux-for-gitops/"&gt;ADR 0003&lt;/a&gt;).&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;MetalLB + Envoy Gateway&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;LoadBalancer IPs on bare metal, and the Gateway API (the successor to Ingress) for routing. Replaced ingress-nginx, which was retired upstream (&lt;a href="https://docs.magelssen.io/decisions/0004-ingress-nginx/"&gt;ADR 0004&lt;/a&gt;, &lt;a href="https://docs.magelssen.io/decisions/0006-envoy-gateway/"&gt;ADR 0006&lt;/a&gt;).&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;cert-manager + Route53&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Real Let&amp;rsquo;s Encrypt certificates through DNS-01, which works without exposing the cluster to the internet.&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;External Secrets + AWS SSM&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;The repo is public, so no secret is stored in Git, not even encrypted. Secrets live in SSM Parameter Store (free tier) and are copied into the cluster. See &lt;a href="https://docs.magelssen.io/cluster/secrets/"&gt;secrets&lt;/a&gt; and &lt;a href="https://docs.magelssen.io/decisions/0005-external-secrets-with-aws-ssm/"&gt;ADR 0005&lt;/a&gt;.&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;kube-prometheus-stack&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Prometheus, Grafana and Alertmanager in one chart, with dashboards for the cluster out of the box. Also the data for sizing resource requests. Alertmanager sends alerts to Telegram and Gmail. Uptime Kuma runs in an LXC on Proxmox, outside the cluster, so it sees the services as a user does (&lt;a href="https://docs.magelssen.io/decisions/0011-alerting-with-alertmanager-and-telegram/"&gt;ADR 0011&lt;/a&gt;, &lt;a href="https://docs.magelssen.io/services/uptime-kuma/"&gt;Uptime Kuma&lt;/a&gt;).&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;local-path + NFS&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Databases on the node&amp;rsquo;s own disk, files on the NAS over NFS. Databases on NFS are slow and corrupt easily. The reasoning: &lt;a href="https://docs.magelssen.io/architecture/storage/"&gt;storage&lt;/a&gt;.&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;CloudNativePG&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Postgres as a Kubernetes operator: one small cluster per app, with failover and backups to S3 later.&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;gluetun&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;VPN as a sidecar for qBittorrent only. Its firewall is the kill switch, and the rest of the media stack stays outside the VPN.&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Hugo + GitHub Pages&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;The docs as a website, built from the same Markdown files that GitHub and Claude read, so there is only one copy. Published from &lt;code&gt;main&lt;/code&gt;, and stays up when the homelab is down (&lt;a href="https://docs.magelssen.io/decisions/0015-hugo-for-the-docs-website/"&gt;ADR 0015&lt;/a&gt;).&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Terraform (planned)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Proxmox VMs and LXCs, and later AWS, as code.&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Ansible (planned)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Configure nodes and rebuild the cluster from freshly installed machines.&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Crossplane + AWS (planned)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Provision cloud resources from Kubernetes.&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;</description></item><item><title/><link>https://docs.magelssen.io/cluster/nodes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/cluster/nodes/</guid><description>&lt;h1 id="kubernetes-nodes"&gt;Kubernetes nodes&lt;a class="anchor" href="#kubernetes-nodes" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;Node settings that live outside Git: packages, kubelet configuration and taints. They were set by&#10;hand in October 2026 and must be repeated on a new or reinstalled node. Later this moves&#10;to Ansible.&lt;/p&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Node&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Role&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;CPU&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;RAM&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Disk&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Allocatable for pods&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;lenovo1&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;control plane, also runs workloads&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;6 cores&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;8 GB&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;~100 GB&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;5500m CPU, ~6.3 GiB&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;lenovo2&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;worker&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;6 cores&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;8 GB&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;~200 GB&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;5500m CPU, ~6.3 GiB&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;pi5&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;worker (arm64)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;4 cores&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;8 GB&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;~480 GB&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;3500m CPU, ~6.5 GiB&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;h2 id="packages"&gt;Packages&lt;a class="anchor" href="#packages" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Every node needs &lt;strong&gt;&lt;code&gt;nfs-common&lt;/code&gt;&lt;/strong&gt;, the NFS client (&lt;code&gt;mount.nfs&lt;/code&gt;). The kubelet mounts the&#10;static NFS PersistentVolumes itself, on whichever node the pod lands. Without it the pod&#10;stays in &lt;code&gt;Init&lt;/code&gt; or &lt;code&gt;ContainerCreating&lt;/code&gt; with &lt;code&gt;mount failed: exit status 32 ... bad option; ... you might need a /sbin/mount.&amp;lt;type&amp;gt; helper program&lt;/code&gt;.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/cluster/secrets/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/cluster/secrets/</guid><description>&lt;h1 id="secrets"&gt;Secrets&lt;a class="anchor" href="#secrets" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;The repository is public, so no secret is ever stored in Git, not even encrypted.&#10;Secrets live in &lt;strong&gt;AWS SSM Parameter Store&lt;/strong&gt; (region &lt;code&gt;eu-west-1&lt;/code&gt;) and&#10;&lt;a href="https://external-secrets.io/"&gt;external-secrets&lt;/a&gt; copies them into the cluster as&#10;normal Kubernetes Secrets.&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;AWS SSM /homelab/&amp;lt;namespace&amp;gt;/&amp;lt;name&amp;gt; (SecureString)&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; │ read by the IAM user homelab-external-secrets&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ▼&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ClusterSecretStore aws-ssm (kubernetes/infrastructure/external-secrets/)&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; │&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ▼&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ExternalSecret in the app&amp;#39;s folder (in Git: only names and paths, no values)&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; │&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ▼&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;Secret in the app&amp;#39;s namespace (created and refreshed by external-secrets)&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id="bootstrap-done-by-hand-not-in-git"&gt;Bootstrap (done by hand, not in Git)&lt;a class="anchor" href="#bootstrap-done-by-hand-not-in-git" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;IAM user &lt;code&gt;homelab-external-secrets&lt;/code&gt; with an inline policy that allows only&#10;&lt;code&gt;ssm:GetParameter&lt;/code&gt;, &lt;code&gt;ssm:GetParameters&lt;/code&gt; and &lt;code&gt;ssm:GetParametersByPath&lt;/code&gt; on&#10;&lt;code&gt;parameter/homelab&lt;/code&gt; and &lt;code&gt;parameter/homelab/*&lt;/code&gt;. SecureStrings use the AWS managed&#10;key &lt;code&gt;aws/ssm&lt;/code&gt;, which needs no extra KMS permission.&lt;/li&gt;&#10;&lt;li&gt;Its access key as the Secret &lt;code&gt;external-secrets/aws-ssm-credentials&lt;/code&gt;&#10;(keys &lt;code&gt;access-key-id&lt;/code&gt; and &lt;code&gt;secret-access-key&lt;/code&gt;).&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;Same pattern as cert-manager&amp;rsquo;s Route53 key. Later this moves to Terraform.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0001-bare-metal-kubernetes-nodes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0001-bare-metal-kubernetes-nodes/</guid><description>&lt;h1 id="kubernetes-on-bare-metal-nodes-not-vms"&gt;Kubernetes on bare-metal nodes, not VMs&lt;a class="anchor" href="#kubernetes-on-bare-metal-nodes-not-vms" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The cluster needed nodes. Proxmox was already there to run VMs, so the nodes could be VMs on&#10;it, or separate physical machines. The lab is for learning Kubernetes the way it runs on real&#10;hardware, and for the Kubernetes certifications.&lt;/p&gt;&#10;&lt;h2 id="options"&gt;Options&lt;a class="anchor" href="#options" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;VMs on Proxmox&lt;/strong&gt;: cheap to make and throw away, with snapshots before risky upgrades. But&#10;the NAS, the hypervisor and the whole cluster would share one machine, so one hardware&#10;failure or Proxmox upgrade takes everything down. The iGPU (for video transcoding) would&#10;need passthrough to one VM.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Kubernetes on the TrueNAS or Proxmox host itself&lt;/strong&gt;: mixes the cluster with the storage.&#10;Rejected for the same reason.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Separate physical machines&lt;/strong&gt; (chosen): two Lenovo ThinkCentre M720q and a Raspberry Pi 5.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="decision"&gt;Decision&lt;a class="anchor" href="#decision" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Chosen: separate physical machines, because the NAS, the hypervisor and the cluster can then&#10;be rebuilt or restarted without touching each other, and the cluster deals with real nodes:&#10;real disks, a real iGPU and two CPU architectures.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0002-truenas-as-a-vm-on-proxmox/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0002-truenas-as-a-vm-on-proxmox/</guid><description>&lt;h1 id="truenas-as-a-vm-on-proxmox"&gt;TrueNAS as a VM on Proxmox&lt;a class="anchor" href="#truenas-as-a-vm-on-proxmox" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;One machine had to hold the disks (NAS) and also run VMs and containers for the&#10;services that are not in Kubernetes (Docker images, Pi-hole, Plex, Tailscale,&#10;the Omada controller). Either the NAS runs the VMs, or a hypervisor runs the&#10;NAS.&lt;/p&gt;&#10;&lt;h2 id="options"&gt;Options&lt;a class="anchor" href="#options" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;TrueNAS on the bare machine, running VMs and apps itself&lt;/strong&gt;: TrueNAS sees the disks&#10;directly. But VMs and apps are not what TrueNAS is built for, and they have&#10;changed a lot between releases. Tried out TrueNAS on the bare machine, but had&#10;problems with a lot of the apps (vms).&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Proxmox only, with ZFS and NFS/SMB set up by hand&lt;/strong&gt;: one layer less, but no NAS interface&#10;for shares, users, snapshot tasks, replication and disk health. All of it by hand on the&#10;hypervisor.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Proxmox on the bare machine, TrueNAS in a VM&lt;/strong&gt; (chosen).&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="decision"&gt;Decision&lt;a class="anchor" href="#decision" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Chosen: Proxmox with TrueNAS in a VM, because each does what it is built for. Proxmox is a&#10;full hypervisor with LXCs, backups, an API and a Terraform provider, and TrueNAS is a full NAS.&#10;The disks are passed through to the TrueNAS VM, so the pool (&lt;code&gt;Firelink&lt;/code&gt;) belongs to TrueNAS&#10;and could move to another machine.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0003-flux-for-gitops/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0003-flux-for-gitops/</guid><description>&lt;h1 id="flux-for-gitops-not-argo-cd"&gt;Flux for GitOps, not Argo CD&lt;a class="anchor" href="#flux-for-gitops-not-argo-cd" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Everything in the cluster should come from Git, applied by a controller in the cluster, so&#10;nothing is applied by hand and every change has a commit. The two big GitOps tools are Flux&#10;and Argo CD. Both are CNCF graduated projects and both pull from Git.&lt;/p&gt;&#10;&lt;h2 id="options"&gt;Options&lt;a class="anchor" href="#options" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Argo CD&lt;/strong&gt;: a web UI that shows every app, its resources and the diff to Git, with&#10;single sign-on and buttons to sync and roll back. More to run (API server, repo server,&#10;Redis, Dex), and the UI makes it easy to change things outside Git. Helm charts are&#10;rendered with &lt;code&gt;helm template&lt;/code&gt;, so they are not real Helm releases.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Flux&lt;/strong&gt; (chosen): a set of small controllers configured only with Kubernetes resources&#10;(&lt;code&gt;GitRepository&lt;/code&gt;, &lt;code&gt;Kustomization&lt;/code&gt;, &lt;code&gt;HelmRelease&lt;/code&gt;). No UI. Helm charts are installed as real&#10;Helm releases by helm-controller.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="decision"&gt;Decision&lt;a class="anchor" href="#decision" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Chosen: Flux, because the lack of a UI means working through &lt;code&gt;kubectl&lt;/code&gt;, &lt;code&gt;flux&lt;/code&gt; and the&#10;manifests, which is the point of the lab, and because Flux is what I use at work.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0004-ingress-nginx/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0004-ingress-nginx/</guid><description>&lt;h1 id="ingress-nginx-for-traffic-into-the-cluster"&gt;ingress-nginx for traffic into the cluster&lt;a class="anchor" href="#ingress-nginx-for-traffic-into-the-cluster" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The apps in the cluster needed to be reached over HTTPS by name, through one IP from MetalLB.&#10;The standard way was an &lt;code&gt;Ingress&lt;/code&gt; resource and an ingress controller. In November 2025 the&#10;Kubernetes project had announced that ingress-nginx would be retired in March 2026, and&#10;pointed to the Gateway API as the successor.&lt;/p&gt;&#10;&lt;h2 id="options"&gt;Options&lt;a class="anchor" href="#options" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Gateway API from the start&lt;/strong&gt; (Envoy Gateway or another controller): the future, but&#10;skips the API that most clusters, charts and guides still use.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Traefik with Ingress&lt;/strong&gt;: also common, but adds its own resources on top.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;ingress-nginx&lt;/strong&gt; (chosen): the most used ingress controller, with &lt;code&gt;Ingress&lt;/code&gt; resources.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="decision"&gt;Decision&lt;a class="anchor" href="#decision" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Chosen: ingress-nginx, on purpose, although it was going to be retired: to get experience&#10;with the &lt;code&gt;Ingress&lt;/code&gt; API that most clusters still run, and then with moving a running cluster&#10;from Ingress to the Gateway API, which many teams have to do now.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0005-external-secrets-with-aws-ssm/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0005-external-secrets-with-aws-ssm/</guid><description>&lt;h1 id="secrets-in-aws-ssm-through-external-secrets"&gt;Secrets in AWS SSM through External Secrets&lt;a class="anchor" href="#secrets-in-aws-ssm-through-external-secrets" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Apps need passwords and keys, and everything else is in Git. The repository is public, so&#10;whatever is in Git can be read by anyone, forever, also after it is deleted. Until then, the&#10;few Secrets in the cluster were made by hand.&lt;/p&gt;&#10;&lt;h2 id="options"&gt;Options&lt;a class="anchor" href="#options" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;SOPS + age&lt;/strong&gt;: secrets encrypted in Git, and Flux decrypts them. Simple and built into&#10;Flux. But the encrypted files are public for good: if the age key ever leaks, every secret&#10;in the history leaks with it.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Sealed Secrets&lt;/strong&gt;: also encrypted in Git, with the same problem. The key is in the cluster,&#10;so rebuilding the cluster without a backup of it means sealing every secret again.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Vault or OpenBao in the cluster&lt;/strong&gt;: a real secrets server, but heavy for a homelab, and it&#10;needs storage, unsealing and its own backups. The cluster would hold the secrets it needs&#10;to start.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;External Secrets + AWS SSM Parameter Store&lt;/strong&gt; (chosen): the secrets live in AWS, and Git&#10;only has the names.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="decision"&gt;Decision&lt;a class="anchor" href="#decision" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Chosen: External Secrets with AWS SSM, because no secret is in Git at all, not even&#10;encrypted, and SSM is free at this size. AWS is already used for Route53.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0006-envoy-gateway/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0006-envoy-gateway/</guid><description>&lt;h1 id="envoy-gateway-gateway-api-instead-of-ingress-nginx"&gt;Envoy Gateway (Gateway API) instead of ingress-nginx&lt;a class="anchor" href="#envoy-gateway-gateway-api-instead-of-ingress-nginx" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;All traffic came in through ingress-nginx (&lt;a href="https://docs.magelssen.io/decisions/0004-ingress-nginx/"&gt;0004&lt;/a&gt;), chosen knowing it&#10;would be retired, so that the move to the Gateway API could be done on a running cluster. The&#10;Kubernetes project stopped fixing ingress-nginx in March 2026 and points to the Gateway API as&#10;the successor to Ingress. Some routes go to services outside the cluster with&#10;self-signed certificates (Proxmox, TrueNAS, Omada), and the Gateway API&amp;rsquo;s own&#10;&lt;code&gt;BackendTLSPolicy&lt;/code&gt; cannot skip certificate checks.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0007-restic-for-laptop-backups/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0007-restic-for-laptop-backups/</guid><description>&lt;h1 id="restic-for-laptop-backups-not-kopia"&gt;restic for laptop backups, not Kopia&lt;a class="anchor" href="#restic-for-laptop-backups-not-kopia" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Laptops need backups to the NAS, also when they are not at home. The backup server runs in&#10;the cluster behind Envoy Gateway, with its data on NFS (&lt;code&gt;Catacombs/backups&lt;/code&gt;). A laptop that&#10;is stolen or hit by ransomware must not be able to delete its own backups.&lt;/p&gt;&#10;&lt;h2 id="options"&gt;Options&lt;a class="anchor" href="#options" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Kopia&lt;/strong&gt;: fast, with a web UI and a repository server with users. But the&#10;server speaks gRPC, which needs HTTP/2 and TLS all the way to the pod, so it needs its own&#10;certificate and extra Envoy settings. The server cannot stop a client from deleting&#10;snapshots.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;BorgBackup&lt;/strong&gt;: mature, but runs over SSH, which does not fit behind the HTTP gateway.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;restic with rest-server&lt;/strong&gt; (chosen): restic encrypts on the laptop, and rest-server is a&#10;small HTTP server for the repositories.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="decision"&gt;Decision&lt;a class="anchor" href="#decision" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Chosen: restic with rest-server, because rest-server has an append-only mode (a laptop can add&#10;backups, but not delete or change them), it works as plain HTTP behind Envoy Gateway, and the&#10;same tool can be used later for the offsite copies.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0008-renovate-for-dependency-updates/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0008-renovate-for-dependency-updates/</guid><description>&lt;h1 id="renovate-for-dependency-updates"&gt;Renovate for dependency updates&lt;a class="anchor" href="#renovate-for-dependency-updates" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Versions are pinned everywhere: Helm charts, images, Flux itself, GitHub Actions (by SHA) and&#10;pre-commit hooks. They were checked by hand once a month against &lt;code&gt;docs/operations/versions.md&lt;/code&gt;, which&#10;was slow and easy to forget. A tool should notice new versions and open pull requests.&lt;/p&gt;&#10;&lt;h2 id="options"&gt;Options&lt;a class="anchor" href="#options" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Dependabot&lt;/strong&gt;: built into GitHub, but has no Flux support (HelmReleases and the Flux&#10;components are not updated), and Kubernetes images need one entry per directory.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Flux image automation&lt;/strong&gt;: runs in the cluster and commits new image tags. Only images, and&#10;it needs write access to the repository.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Updatecli&lt;/strong&gt;: flexible, but every dependency needs a hand-written rule.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Renovate&lt;/strong&gt; (chosen): understands Flux, Kubernetes manifests, SHA-pinned actions and&#10;pre-commit, with grouping, schedules and a minimum release age built in.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="decision"&gt;Decision&lt;a class="anchor" href="#decision" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Chosen: Renovate, as the hosted Mend Renovate app, because it covers almost everything pinned&#10;in the repository and needs nothing running in the homelab.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0009-github-app-for-flux/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0009-github-app-for-flux/</guid><description>&lt;h1 id="a-github-app-for-fluxs-commit-statuses"&gt;A GitHub App for Flux&amp;rsquo;s commit statuses&lt;a class="anchor" href="#a-github-app-for-fluxs-commit-statuses" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Flux posts a commit status to GitHub for each commit it applies, so GitHub shows what actually&#10;runs in the cluster. For that, the cluster needs a login to GitHub that can write commit&#10;statuses. The repository is public, and the login is stored in the cluster.&lt;/p&gt;&#10;&lt;h2 id="options"&gt;Options&lt;a class="anchor" href="#options" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Classic personal access token&lt;/strong&gt;: the &lt;code&gt;repo&lt;/code&gt; scope gives full access to all my&#10;repositories. Far too much.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Fine-grained personal access token&lt;/strong&gt;: can be limited to commit statuses on one&#10;repository. But it belongs to my account, the statuses show up as me, and it has to be&#10;renewed when it expires.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Deploy key&lt;/strong&gt;: SSH access to Git only. It cannot post statuses.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;GitHub App&lt;/strong&gt; (chosen): its own identity, installed on this repository only, with the one&#10;permission it needs.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="decision"&gt;Decision&lt;a class="anchor" href="#decision" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Chosen: a GitHub App (&lt;code&gt;larma-homelab-flux&lt;/code&gt;), because it has the least access, is not tied to&#10;my account, and shows up as its own bot. Flux supports App logins directly.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0010-no-bot-account-for-claude/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0010-no-bot-account-for-claude/</guid><description>&lt;h1 id="no-bot-account-or-auto-approval-for-claudes-pull-requests"&gt;No bot account or auto-approval for Claude&amp;rsquo;s pull requests&lt;a class="anchor" href="#no-bot-account-or-auto-approval-for-claudes-pull-requests" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Claude Code writes most changes in this repository, on a branch. I read them, commit them&#10;under my own name (with a &lt;code&gt;Co-Authored-By&lt;/code&gt; line for Claude), open the pull request and merge&#10;it. The ruleset on &lt;code&gt;main&lt;/code&gt; requires a pull request and the checks, but 0 approvals, because&#10;GitHub does not let anyone approve their own pull request. So OpenSSF Scorecard gives a low&#10;Code-Review score, and the rule &amp;ldquo;a change needs an approval&amp;rdquo; cannot be turned on.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0011-alerting-with-alertmanager-and-telegram/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0011-alerting-with-alertmanager-and-telegram/</guid><description>&lt;h1 id="alerts-from-alertmanager-to-telegram-and-uptime-kuma-moved-to-proxmox"&gt;Alerts from Alertmanager to Telegram, and Uptime Kuma moved to Proxmox&lt;a class="anchor" href="#alerts-from-alertmanager-to-telegram-and-uptime-kuma-moved-to-proxmox" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Prometheus and Alertmanager run in the cluster (kube-prometheus-stack), with the chart&amp;rsquo;s default&#10;alert rules, but Alertmanager has no receiver: alerts fire and nobody is told. On 2026-11-17 all&#10;sites were down for 29 minutes while every pod was healthy and Flux was green. It was found by&#10;chance.&lt;/p&gt;&#10;&lt;p&gt;Uptime Kuma also runs in the cluster, and it showed no downtime. From a pod, kube-proxy sends&#10;traffic for a LoadBalancer IP straight to the backend pod (the Service has &lt;code&gt;ipMode: VIP&lt;/code&gt;). The&#10;check never asks the network who has 192.168.30.200, so it skips MetalLB, which is the part that&#10;broke. Anything in the cluster also goes down with the cluster, so it cannot report that.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0012-pihole-stays-in-an-lxc/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0012-pihole-stays-in-an-lxc/</guid><description>&lt;h1 id="pi-hole-stays-in-an-lxc-on-proxmox-not-in-kubernetes"&gt;Pi-hole stays in an LXC on Proxmox, not in Kubernetes&lt;a class="anchor" href="#pi-hole-stays-in-an-lxc-on-proxmox-not-in-kubernetes" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The goal is to move the services on Proxmox into Kubernetes. Pi-hole (LXC 104,&#10;&lt;code&gt;192.168.20.20&lt;/code&gt;) is the DNS server for the whole home network: it answers internet&#10;lookups for every client, and it holds the local records that point the Kubernetes&#10;hostnames (&lt;code&gt;*.magelssen.io&lt;/code&gt;) to the Envoy Gateway at &lt;code&gt;192.168.30.200&lt;/code&gt;. Unlike the&#10;other services, the cluster itself depends on it.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0013-uptime-kuma-without-docker/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0013-uptime-kuma-without-docker/</guid><description>&lt;h1 id="uptime-kuma-installed-with-nodejs-in-its-lxc-not-in-docker"&gt;Uptime Kuma installed with Node.js in its LXC, not in Docker&lt;a class="anchor" href="#uptime-kuma-installed-with-nodejs-in-its-lxc-not-in-docker" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;&lt;a href="https://docs.magelssen.io/decisions/0011-alerting-with-alertmanager-and-telegram/"&gt;ADR 0011&lt;/a&gt; moved Uptime Kuma out of the&#10;cluster into an LXC on Proxmox. That left how to run it inside the LXC. Uptime Kuma ships a&#10;Docker image (which the cluster used) and supports a plain Node.js install from source.&#10;The old docker LXC (102), which ran Docker with Portainer, was just retired.&lt;/p&gt;&#10;&lt;h2 id="options"&gt;Options&lt;a class="anchor" href="#options" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Docker in the LXC&lt;/strong&gt;: the same image as in the cluster. But Proxmox recommends running&#10;application containers in a VM, not in an LXC; Docker in an unprivileged LXC needs&#10;&lt;code&gt;nesting&lt;/code&gt; and &lt;code&gt;keyctl&lt;/code&gt; and breaks now and then on Proxmox or kernel updates. It adds a&#10;daemon and a layer for one app.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;A small VM with Docker&lt;/strong&gt;: what Proxmox recommends for Docker, but a full VM (kernel,&#10;more RAM and disk) for one small Node.js app.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Node.js in the LXC&lt;/strong&gt; (chosen): Uptime Kuma&amp;rsquo;s documented install without Docker, git tag&#10;pinned, run by systemd.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="decision"&gt;Decision&lt;a class="anchor" href="#decision" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Chosen: Node.js in the LXC, because it is the simplest setup that Proxmox supports well,&#10;and it fits being managed by Ansible later. Debian 13 ships a new enough Node.js (20.19,&#10;Uptime Kuma 2.x needs 20.4 or newer), so no extra apt repository is needed.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0014-infrastructure-services-stay-outside-kubernetes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0014-infrastructure-services-stay-outside-kubernetes/</guid><description>&lt;h1 id="services-needed-to-run-or-fix-the-cluster-stay-outside-kubernetes"&gt;Services needed to run or fix the cluster stay outside Kubernetes&lt;a class="anchor" href="#services-needed-to-run-or-fix-the-cluster-stay-outside-kubernetes" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The goal has been to move the services on Proxmox into Kubernetes. Two exceptions were made&#10;one at a time: Pi-hole (&lt;a href="https://docs.magelssen.io/decisions/0012-pihole-stays-in-an-lxc/"&gt;ADR 0012&lt;/a&gt;) and Uptime Kuma&#10;(&lt;a href="https://docs.magelssen.io/decisions/0011-alerting-with-alertmanager-and-telegram/"&gt;ADR 0011&lt;/a&gt;). The next candidate was the&#10;Omada controller (issue #102), which manages the router, the switch and the access point.&#10;It raised the same question a third time, so this record turns the exceptions into a rule.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/decisions/0015-hugo-for-the-docs-website/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/decisions/0015-hugo-for-the-docs-website/</guid><description>&lt;h1 id="a-hugo-website-built-from-docs-published-to-github-pages"&gt;A Hugo website built from docs/, published to GitHub Pages&lt;a class="anchor" href="#a-hugo-website-built-from-docs-published-to-github-pages" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;h2 id="context"&gt;Context&lt;a class="anchor" href="#context" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The documentation is Markdown in &lt;code&gt;docs/&lt;/code&gt;. It is read on GitHub, and by Claude&#10;from the files. A website with navigation and search makes it easier to read, but a separate&#10;wiki or a second copy of the text would drift away from the repository, and Claude could not&#10;read it. So the website must be built from the same files, without changing how they read&#10;on GitHub: no generator-only syntax, relative links to &lt;code&gt;.md&lt;/code&gt; files, &lt;code&gt;README.md&lt;/code&gt; as the index of&#10;a directory, and the title as the first &lt;code&gt;# heading&lt;/code&gt;.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/development/claude-agent/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/development/claude-agent/</guid><description>&lt;h1 id="claude-as-an-agent-in-the-homelab"&gt;Claude as an agent in the homelab&lt;a class="anchor" href="#claude-as-an-agent-in-the-homelab" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;Claude Code has &lt;strong&gt;read-only&lt;/strong&gt; access to the homelab. All changes go through Git and&#10;are rolled out by Flux (or by a human), never by Claude directly.&lt;/p&gt;&#10;&lt;h2 id="how-access-is-limited"&gt;How access is limited&lt;a class="anchor" href="#how-access-is-limited" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Claude can inspect the cluster and propose changes, but it cannot change anything by&#10;itself:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Read-only ServiceAccount: &lt;code&gt;claude-readonly&lt;/code&gt; is bound to the built-in &lt;code&gt;view&lt;/code&gt;&#10;ClusterRole plus a small extra ClusterRole for nodes, persistent volumes, CRDs,&#10;Flux, Prometheus Operator and Gateway API resources, and may run PromQL queries&#10;through the Prometheus Service. It has no access to secrets. The RBAC is managed by Flux like&#10;everything else, in &lt;a href="https://github.com/l4rma/homelab/blob/main/kubernetes/infrastructure/claude-readonly"&gt;&lt;code&gt;kubernetes/infrastructure/claude-readonly&lt;/code&gt;&lt;/a&gt;.&lt;/li&gt;&#10;&lt;li&gt;Separate kubeconfig: a &lt;a href="https://github.com/l4rma/homelab/blob/main/scripts/create-claude-kubeconfig.sh"&gt;script&lt;/a&gt; builds a&#10;kubeconfig from the ServiceAccount token. Claude Code uses it through a gitignored&#10;local settings file. The admin kubeconfig is denied.&lt;/li&gt;&#10;&lt;li&gt;Client-side guardrails: &lt;a href="https://github.com/l4rma/homelab/blob/main/.claude/settings.json"&gt;&lt;code&gt;.claude/settings.json&lt;/code&gt;&lt;/a&gt; allows&#10;read commands and denies &lt;code&gt;kubectl apply/delete/edit/patch/exec&lt;/code&gt; and&#10;&lt;code&gt;flux reconcile/suspend&lt;/code&gt;.&lt;/li&gt;&#10;&lt;li&gt;Changes through Git: Claude works on a branch. A human reviews, commits and merges,&#10;and Flux rolls out the change.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Why it is set up this way: the RBAC is enforced by the API server, so even if a&#10;client-side rule is bypassed, the agent still cannot change the cluster or read&#10;secrets. Every change goes through review and is recorded in Git history, the same&#10;as for a human operator. The repo is public, so no credentials are ever part of the&#10;setup in Git.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/development/github/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/development/github/</guid><description>&lt;h1 id="github-repository"&gt;GitHub repository&lt;a class="anchor" href="#github-repository" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;How the repository itself is set up. Settings that cannot live in Git are listed here, so&#10;they can be checked and set again by hand.&lt;/p&gt;&#10;&lt;h2 id="ruleset-on-main"&gt;Ruleset on &lt;code&gt;main&lt;/code&gt;&lt;a class="anchor" href="#ruleset-on-main" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Defined in &lt;a href="https://github.com/l4rma/homelab/blob/main/.github/rulesets/main.json"&gt;&lt;code&gt;.github/rulesets/main.json&lt;/code&gt;&lt;/a&gt;. GitHub does not&#10;read the file by itself. Apply a change with:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-sh" data-lang="sh"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;gh api -X PUT repos/l4rma/homelab/rulesets/&amp;lt;id&amp;gt; --input .github/rulesets/main.json&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;(&lt;code&gt;gh api repos/l4rma/homelab/rulesets&lt;/code&gt; lists the id. The first time, use&#10;&lt;code&gt;gh api -X POST repos/l4rma/homelab/rulesets --input .github/rulesets/main.json&lt;/code&gt;, or import&#10;the file under Settings → Rules → Rulesets.)&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/operations/backups/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/operations/backups/</guid><description>&lt;h1 id="backups"&gt;Backups&lt;a class="anchor" href="#backups" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;What is backed up, where, and how to restore it. Everything here is local: the copies are&#10;in the same pool as the data, so losing the pool loses both. Offsite copies come later.&lt;/p&gt;&#10;&lt;h2 id="zfs-snapshots-truenas"&gt;ZFS snapshots (TrueNAS)&lt;a class="anchor" href="#zfs-snapshots-truenas" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;Periodic snapshot tasks under Data Protection. A snapshot protects against deleting or&#10;overwriting files, not against losing the pool.&lt;/p&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Dataset&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Schedule&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Kept&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;AnorLondo&lt;/code&gt; (recursive)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Daily&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;30 days&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;BlightTown&lt;/code&gt; (recursive), &lt;code&gt;UndeadParish&lt;/code&gt; (recursive), &lt;code&gt;Catacombs&lt;/code&gt; (recursive)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Daily&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;14 days&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;DukesArchives&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Weekly (Sunday)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;2 weeks&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;p&gt;&amp;ldquo;Allow taking empty snapshots&amp;rdquo; is on for every task. Each snapshot expires when its time is&#10;up, whether or not a newer one exists: without it, a dataset that does not change for longer&#10;than the retention ends up with no snapshot at all. An unchanged snapshot only costs a few KB&#10;of metadata.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/operations/dependencies/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/operations/dependencies/</guid><description>&lt;h1 id="dependency-updates-renovate"&gt;Dependency updates (Renovate)&lt;a class="anchor" href="#dependency-updates-renovate" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;&lt;a href="https://docs.renovatebot.com/"&gt;Renovate&lt;/a&gt; watches every version pinned in this repository and&#10;opens a pull request when a newer one is out. The configuration is&#10;&lt;a href="https://github.com/l4rma/homelab/blob/main/.github/renovate.json5"&gt;&lt;code&gt;.github/renovate.json5&lt;/code&gt;&lt;/a&gt;. It runs as the&#10;&lt;a href="https://github.com/apps/renovate"&gt;Mend Renovate GitHub App&lt;/a&gt; (free, hosted by Mend), and&#10;nothing runs in the homelab.&lt;/p&gt;&#10;&lt;h2 id="what-it-watches"&gt;What it watches&lt;a class="anchor" href="#what-it-watches" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Where&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;What&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Renovate manager&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;kubernetes/**/helmrelease.yaml&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Helm chart versions, looked up in the matching HelmRepository&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;flux&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;kubernetes/clusters/homelab/flux-system/gotk-components.yaml&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Flux itself. The pull request regenerates the whole file, like &lt;code&gt;flux install --export&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;flux&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;kubernetes/**&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Container images (&lt;code&gt;image:&lt;/code&gt;) in Deployments, DaemonSets and upstream manifests&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;kubernetes&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;kubernetes/apps/immich/postgres-cluster.yaml&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;The CloudNativePG image (&lt;code&gt;imageName:&lt;/code&gt;)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;regex&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;.github/workflows/&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Actions (the SHA and the version comment together), the flux-schema image, the pre-commit version, Hugo (&lt;code&gt;HUGO_VERSION&lt;/code&gt;)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;github-actions&lt;/code&gt;, regex&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;.pre-commit-config.yaml&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Hook revisions (&lt;code&gt;rev: &amp;lt;sha&amp;gt; # frozen: vX.Y.Z&lt;/code&gt;)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;pre-commit&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;hugo/go.mod&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;The docs website&amp;rsquo;s theme (hugo-book), a Hugo module&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;gomod&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;p&gt;Not in Git, so not seen by Renovate: Proxmox, TrueNAS, the node OS, Kubernetes itself&#10;(kubeadm), containerd, Flannel and everything in the LXCs. Those stay in&#10;&lt;a href="https://docs.magelssen.io/operations/versions/"&gt;versions.md&lt;/a&gt;.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/operations/versions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/operations/versions/</guid><description>&lt;h1 id="versions"&gt;Versions&lt;a class="anchor" href="#versions" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;What Renovate cannot see: the hosts, Kubernetes itself, and the services outside&#10;Kubernetes. Everything pinned in Git (Helm charts, images, Flux, actions, pre-commit hooks)&#10;is watched by Renovate, and its Dependency Dashboard issue lists what is behind. See&#10;&lt;a href="https://docs.magelssen.io/operations/dependencies/"&gt;dependencies.md&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Last check: 2026-10-31.&lt;/strong&gt; Next check: first weekend of each month.&lt;/p&gt;&#10;&lt;h2 id="monthly-check"&gt;Monthly check&lt;a class="anchor" href="#monthly-check" aria-label="Link"&gt;&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Compare the running versions below with the sources, and update the tables and the&#10;&lt;strong&gt;Last check&lt;/strong&gt; date, also when nothing changed.&lt;/li&gt;&#10;&lt;li&gt;Read the release notes before updating anything that is behind, and move newly found&#10;problems to &lt;a href="#needs-attention"&gt;Needs attention&lt;/a&gt;.&lt;/li&gt;&#10;&lt;li&gt;Look through the Dependency Dashboard for updates that wait for approval (majors).&lt;/li&gt;&#10;&lt;li&gt;Update one thing per PR, and add a line to the &lt;a href="#update-log"&gt;update log&lt;/a&gt; in the same PR.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;Claude can do steps 1 to 3 with its read-only access, except for the versions marked&#10;&amp;ldquo;check by hand&amp;rdquo; below.&lt;/p&gt;</description></item><item><title/><link>https://docs.magelssen.io/services/uptime-kuma/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.magelssen.io/services/uptime-kuma/</guid><description>&lt;h1 id="uptime-kuma"&gt;Uptime Kuma&lt;a class="anchor" href="#uptime-kuma" aria-label="Link"&gt;&lt;/a&gt;&lt;/h1&gt;&#10;&lt;p&gt;Uptime Kuma runs in LXC 101 on Proxmox, outside the cluster, so it checks the services the&#10;way a browser on the LAN does and keeps running when the cluster is down&#10;(&lt;a href="https://docs.magelssen.io/decisions/0011-alerting-with-alertmanager-and-telegram/"&gt;ADR 0011&lt;/a&gt;). It is installed&#10;from source with Node.js, not Docker&#10;(&lt;a href="https://docs.magelssen.io/decisions/0013-uptime-kuma-without-docker/"&gt;ADR 0013&lt;/a&gt;).&lt;/p&gt;&#10;&lt;p&gt;The LXC is set up by hand until Terraform and Ansible cover Proxmox (#104). These are the&#10;steps that were used, so it can be rebuilt.&lt;/p&gt;</description></item></channel></rss>