A number of fixes to get things running

2026-10-03 09:43:45 -06:00
parent cb47e319df
commit 461b0889e6
10 changed files with 2035 additions and 10 deletions
@@ -23,3 +23,50 @@ sudo virt-install --virt-type kvm --name worker-node-1 --ram 4096 --vcpus 4 --di
 ```

 Note that the VMs are booted into the ISO and terraform initiates the install and cluster build.
+
+## Upgrade Talos from 1.13 to 1.14
+
+Talos 1.14 no longer publishes the release installer image at `ghcr.io/siderolabs/installer:v1.14.0`. Use the Talos Image Factory installer image with the generic amd64 KVM schematic:
+
+```bash
+export TALOSCONFIG="$HOME/.talos/home-services/talosconfig"
+
+export TALOS_INSTALLER_IMAGE="factory.talos.dev/metal-installer/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba:v1.14.0"
+```
+
+Upgrade the worker first:
+
+```bash
+talosctl upgrade \
+	--endpoints 10.0.0.246 \
+	--nodes 10.0.0.246 \
+	--image "$TALOS_INSTALLER_IMAGE" \
+	--wait
+```
+
+After the worker is healthy, upgrade the control-plane node:
+
+```bash
+talosctl upgrade \
+	--endpoints 10.0.0.99 \
+	--nodes 10.0.0.99 \
+	--image "$TALOS_INSTALLER_IMAGE" \
+	--wait
+```
+
+Verify both nodes before reconciling Terraform:
+
+```bash
+talosctl version --endpoints 10.0.0.246 --nodes 10.0.0.246
+talosctl version --endpoints 10.0.0.99 --nodes 10.0.0.99
+talosctl health --endpoints 10.0.0.99 --nodes 10.0.0.99,10.0.0.246
+```
+
+Then update `terraform.tfvars` to `talos_version = "v1.14.0"` if needed and run:
+
+```bash
+terraform plan
+terraform apply
+```
+
+Do not use `talosctl reset` or recreate the VMs for this upgrade. The installer preserves the Talos state and Kubernetes data.