Adapt Talos config for five-node mixed architecture cluster

talos/patch-longhorn.yaml

@@ -1,6 +1,7 @@
-# Prepares each node for Longhorn (apps/longhorn.yaml) — the storage layer
-# this repo ships pre-installed. Applied identically to all three
-# control-plane nodes, alongside patch-controlplane.yaml.
+# Prepares each dedicated worker for Longhorn (apps/longhorn.yaml) — the
+# storage layer this repo ships pre-installed. Applied to worker.yaml only;
+# the three Raspberry Pi control-plane nodes do not provide application
+# storage.
 #
 # This file has TWO documents (separated by `---`), because it's making two
 # different kinds of change: a patch to the normal machine config, and a
@@ -22,11 +23,10 @@
 # A Talos UserVolumeConfig tells Talos itself to find, format, and mount a
 # disk — no manual partitioning on your part. `diskSelector.match:
 # '!system_disk'` means "any disk that isn't the one Talos is installed
-# on" (never touches your OS disk), and `minSize: 900GiB` means "only
-# consider disks at least that large" — so if a node has more than one
-# extra disk, Talos won't accidentally pick a small one. Adjust `minSize`
-# if your nodes' data disks are smaller than 900GiB; just make sure it's
-# still large enough to exclude anything that *isn't* meant for Longhorn.
+# on" (never touches your OS disk), and `minSize: 300GiB` means "only
+# consider disks at least that large." Each worker has one 350GiB data disk
+# and one 20GiB system disk, so this admits the intended data disk while
+# rejecting the boot disk.
 # `grow: false` keeps the volume at its initial size even if the
 # underlying disk is later resized — deliberate here, so growing storage
 # is always a conscious decision (see docs/09-growing-up.md).
@@ -56,5 +56,5 @@ name: longhorn
 provisioning:
   diskSelector:
     match: "!system_disk"
-  minSize: 900GiB
+  minSize: 300GiB
   grow: false