[Concept] : Add Intel NUC worker nodes to existing Talos KBVE cluster

[Fudster]

Add Intel NUC worker nodes to existing Talos Linux cluster

Overview

We have an existing Talos Linux control plane running on Hetzner and want to add Intel NUCs as worker nodes with Wireguard networking for secure communication.

Hardware Status

• Intel NUCs: ✅ Available
• PSUs: 🛒 Need to purchase
• RAM: 🛒 Need to purchase (8GB per NUC)
• SSDs: 🛒 Need to purchase

Current Infrastructure

• Control Plane: ✅ Running on Hetzner (single Talos node with Longhorn)
• Wireguard Config: ❌ Need to configure in machine configs

Proposed Implementation

I think we should approach this in the following way:

Phase 1: Hardware Preparation

• Purchase compatible PSUs for our Intel NUC models
• Purchase 8GB RAM per NUC
• Purchase SSDs (recommend 256GB+ per NUC)
• Assemble and test all NUC units

Phase 2: Create Wireguard Network Configuration

• Generate cluster configs with Wireguard networking:

  talosctl cluster create --wireguard-cidr 10.1.0.0/24

• This automatically generates Wireguard network configuration for each node

Phase 3: Extract Configuration Files

• Extract the generated configuration files:

  talosctl get mc v1alpha1 -o jsonpath='{.spec}' -n 10.5.0.2 > controlplane.yaml
  talosctl get mc v1alpha1 -o jsonpath='{.spec}' -n 10.5.0.3 > worker.yaml

Phase 4: Talos Linux Installation on NUCs

• Create Talos Linux ISO/image
• Create bootable USB drives
• Boot each NUC from USB and install Talos Linux to SSD

Phase 5: Join NUCs to Cluster

• Apply worker configuration to each NUC:

  talosctl apply-config --insecure --nodes [NUC_IP] --file worker.yaml

• Verify each NUC joins the cluster successfully
• Test Wireguard connectivity:

  wg show

• Add additional nodes using the scaling procedure:

  talosctl apply-config --insecure --nodes [NODE_IP] --file worker.yaml

• Verify Wireguard mesh connectivity between all nodes
• Test cluster functionality and networking

Questions/Decisions Needed

• How many NUC worker nodes are we adding?
• Do we need any specific hardware requirements based on workload?
• What's the Wireguard CIDR already configured on the Hetzner control plane?

Technical Considerations

• Existing Hetzner control plane should have Wireguard configuration
• NUC workers will connect to Hetzner control plane via Wireguard
• Each NUC will get assigned an IP in the existing Wireguard network range
• 8GB RAM per NUC should be sufficient for most worker node workloads

Resources

• [Talos Linux Wireguard Documentation](https://www.talos.dev/v1.10/talos-guides/network/wireguard-network/)
• [Scaling Talos Clusters](https://www.talos.dev/v1.10/talos-guides/howto/scaling-up/)

---

[BChip]

Copilot, get to work now

[Fudster]

Copilot, get to work now

@BChip I updated the ticket, rerun it please.

[h0lybyte]

@Fudster thanks for taking the time out for making the issue ticket, a lot of people, FAKE NEWS, waste the time, You are amazing for helping us and presenting this issue ticket, I hope you continue to make more.

[h0lybyte]

there was a comment there but it seems that github deletes the comments when the cameras reset.

[BChip]

https://www.amazon.com/dp/B01IU8AWI8

https://www.amazon.com/ALITOVE-Converter-Transformer-100V-240V-Widescreen/dp/B07Z4T115Y

https://www.amazon.com/TEAMGROUP-1600MHz-PC3-12800-204-Pin-Notebook/dp/B0191WAGE2

https://www.amazon.com/Patriot-Burst-Elite-120GB-Solid/dp/B08LKMQ9T4

@h0lybyte This is everything needed

Max 8gb per nuc ddr3 1600mhz

I recommend Ubuntu server LTS and headless install does work as long as you use Ethernet right off the bat