Skip to content

Talos

The talos stack creates every node as a Proxmox VM and turns them into a Talos Linux cluster named talos-cluster. Talos docs.

Sourcetalos.go, proxmox.go, config.yml
VersionsTalos, Kubernetes and image schematics in versions.yaml; see the software inventory
Endpointhttps://192.168.1.210:6443
Outputscore/talosconfig, core/kubeconfig, stack outputs talosconfig, kubeconfig, <node>-ip

Node sizes, images and per-role patches are on Nodes.

flowchart LR
  I[Download base + GPU<br/>images to Proxmox] --> V[Create VMs]
  S[Machine secrets<br/>protected] --> C[Per-node config<br/>hostname, static IP]
  V --> A[Apply config]
  C --> A
  A --> B[Bootstrap etcd on<br/>k8s-controller1]
  B --> K[kubeconfig → platform stack]
SettingValueWhy
CNInoneCilium is installed by the platform stack
kube-proxyDisabledCilium replaces it
install.disk/dev/sdaNodes boot with talos.platform=metal, whose installer refuses to upgrade without it
install.imageUnsetjust talos-upgrade passes the Image Factory installer explicitly
KubernetesVersionPinnedLeft unset, the provider’s default would roll nodes back on apply
Machine secretsprotect: trueThe provider regenerates the cluster PKI if the Talos version decreases
VM imageignoreChanges on the disk’s file IDA newer image must not replace running nodes

Configs are applied to the address the QEMU guest agent reports, falling back to the static IP when the VM is stopped so one stopped node does not block the preview.

Terminal window
just core talos up # create or reconfigure nodes
just talos-health
just talos-versions
just talos-upgrade <ip> # one node at a time
just talos-upgrade 192.168.1.224 gpu # worker4 needs the GPU schematic
just talos-upgrade-k8s
cd core && pulumi stack output talosconfig --show-secrets > ~/.talos/config # refresh a stale talosconfig

Upgrade procedures live under Upgrades.

talosctl cannot connect or rejects the certificate

Section titled “talosctl cannot connect or rejects the certificate”

The local talosconfig is stale. Refresh it from the stack output above and use endpoint 192.168.1.210.

Changing the image did nothing to existing nodes

Section titled “Changing the image did nothing to existing nodes”

By design: the image only seeds new VMs. Upgrade in place with just talos-upgrade <ip>.