Stable predictable interface names (net.ifnames=1) — fixes the v30iot NIC shuffle #375

Merged

k.renner merged 4 commits from claude-bot/talos-predictable-naming into master 2026-07-23 14:29:33 +00:00

Conversation 5 Commits 4 Files Changed 15

+67 -61

4 Commits

Author	SHA1	Message	Date
claude-botandClaude Fable 5	3939fe51f6	fix(ci): ash-portable schematic substring; actually finish the eth1 sweep ... Review blocker: my previous filename fix used bash substring syntax ${TALOS_SCHEMATIC:0:12}, but the apply step runs under busybox ash (Alpine /bin/sh) which errors 'Bad substitution' — the repo already uses cut for this exact reason. Replaced with $(echo "$TALOS_SCHEMATIC" | cut -c1-12). The HCL substr() in talos_image.tf is unaffected (not shell). Also finishes the comment sweep the prior commit claimed but didn't: 4 more stale 'eth1' host-NIC references in the matter/otbr/music-assistant NAD headers are now ens19. Grep confirms zero eth1 left in the v30iot NAD/deployment files. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014S5CLfizEtzHS51kxJFQgc	2026-07-23 16:21:37 +02:00
claude-botandClaude Fable 5	b762cc7941	docs(nad): finish the eth1->ens19 comment sweep in the NAD headers ... Review follow-up (optional): the shelly/matter/otbr NAD header comments still described the old eth1 probe-order naming, contradicting this PR's own root-cause writeup. Updated to the stable ens19 predictable name and dropped the stale k8s-edge/probe-order narration. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014S5CLfizEtzHS51kxJFQgc	2026-07-23 16:12:23 +02:00
claude-botandClaude Fable 5	7eb2e02b1d	fix(ci): key Talos image cache on schematic; reconcile stale comments ... Review blocker: the Proxmox image-exists check derived TALOS_FILENAME from version only, so bumping the schematic left the cached filename unchanged — a future VM (re)provision would find the stale old-schematic image and skip the download, silently reintroducing net.ifnames=0. Embed the schematic hash in the filename (pipeline + opentofu/talos_image.tf, kept in sync) so a schematic bump forces a fresh download. Also reconciles stale comments the rename left behind: the MA reconcile docstring (hostNetwork-era eth1 explanation), cluster.yaml kubelet nodeIP (eth1->ens19), and the matter NAD's k8s-edge claim (edge isn't migrated and isn't a current node; the pod is pinned off it anyway). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014S5CLfizEtzHS51kxJFQgc	2026-07-23 15:59:18 +02:00
claude-botandClaude Fable 5	4ee087ec5b	fix(talos): stable predictable interface names (net.ifnames=1) for v30iot ... Root cause of the IoT NIC name shuffle: the nocloud platform driver unconditionally injects net.ifnames=0, disabling systemd predictable naming, so eth0/1/2 followed driver-probe order and renamed across reboots (a k8s-3 reboot put the v30iot NIC on eth2 and mgmt on eth1, silently mis-targeting the v6-disable sysctl onto mgmt and attaching macvlan children to the Server VLAN). LinkAliasConfig cannot fix this (it only sets a cosmetic IFLA_IFALIAS, invisible to sysctl/CNI). Fix: re-enable predictable naming via a new Image Factory schematic (extraKernelArgs: -net.ifnames=0, net.ifnames=1). Because the cluster boots sd-boot/UKI, the cmdline is baked into the image — machine.install extraKernelArgs is silently ignored — so this MUST be delivered as a schematic + talosctl upgrade, not a config patch. The busPath-derived names are topology-stable and identical across the three identical VMs: 0000:06:13.0 (v30iot) -> ens19 0000:06:12.0 (mgmt) -> ens18 0000:02:00.0 (ceph) -> enp2s0np1 Re-keys everything that referenced the volatile eth1 onto the stable ens19: the four v30iot macvlan NADs (matter/otbr/shelly/music-assistant) and the per-node v6-disable sysctl. Bumps the schematic id in the deploy pipeline. Applied live via rolling talosctl upgrade (one node at a time, full Ceph recovery between each); verified ens19 identical on all three, v30iot NIC addressless v4+v6, macvlan children retain their own v6. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014S5CLfizEtzHS51kxJFQgc	2026-07-23 15:47:42 +02:00