Upgrade note: apply this VolumeConfig patch before upgrading, otherwise affected workloads will fail after the next reboot. Longhorn v2 (SPDK data engine) runs the data plane inside the instance manager process and is not affected. The '--mode=reboot' option has been removed from the talosctl ...

Specifies which node to upgrade. You can specify one node at a time (recommended) or multiple nodes: # Single node (recommended) talosctl upgrade --nodes 192.168.1.10 \ --image ghcr.io/siderolabs/installer:v1.7.0 # Multiple nodes (they will be upgraded sequentially) talosctl upgrade --nodes 192.168.1.10,192.168.1.11 \ --image ghcr.io/siderolabs/installer:v1.7.0

April 19, 2025 - I put it back in maintenance and tried to upgrade: ❯ talosctl upgrade --nodes 192.168.40.7 --image factory.talos.dev/installer/f9355a00f82a90f7dda4b0548c181fc96a2bdc14fd5eea61542b90562ed339ae:v1.9.4 --insecure --wait=false error performing upgrade: rpc error: code = Unimplemented desc = API is not implemented in maintenance mode

January 21, 2025 - Once Nodes have been upgraded, upgrade the talosctl client so the version matches the Talos node version. ... You can also download a specific release from https://github.com/siderolabs/talos/releases, e.g.

June 11, 2025 - talosctl Should not create an impossible situation to recover from (upgrade k8s past os supported version)#11198

March 3, 2026 - Every Talos release has release notes that document breaking changes, new features, and upgrade requirements. Always read these before starting. # Check your current Talos version talosctl version --nodes 192.168.1.10 # Check the latest available version # Visit https://github.com/siderolabs/talos/releases

Make sure the Talos version you are upgrading to supports the Kubernetes version you want to run: # Check current Kubernetes version kubectl version --short # The Talos release notes specify which Kubernetes versions are supported ... # Snapshot etcd talosctl etcd snapshot /tmp/etcd-backup-pre-upgrade.snapshot \ --nodes 192.168.1.10 # Keep a copy of your machine configuration talosctl get machineconfig --nodes 192.168.1.10 -o yaml > cp-01-config-backup.yaml

January 20, 2025 - talosctl upgrade --preserve=true --help Upgrade Talos on the target node Usage: talosctl upgrade [flags] Flags: --debug debug operation from kernel logs.

$ docker pull ghcr.io/siderolabs/talosctl:v1.13.5-14-g9d8e47dd3@sha256:fe8c3b0660c8d09c6396de42a6ad250ef42dafda830f97a8c39470fdefdff7a9

March 3, 2026 - The talosctl upgrade-k8s command makes Kubernetes upgrades on Talos Linux straightforward and reliable. By following the practices outlined here, you can keep your Kubernetes version current while minimizing risk to your workloads.

March 3, 2026 - The talosctl upgrade-k8s command upgrades these components: ... Your CNI plugin (Flannel, Cilium, Calico, etc.) is managed separately from the Kubernetes upgrade. After upgrading Kubernetes, you may need to upgrade the CNI to maintain compatibility: ...

May 15, 2026 - Somehow stuck on outdated Kubernetes version, `talosconfig apply` or `talosctl upgrade-k8s` refuse to update #13361

March 3, 2026 - # Stage the upgrade - downloads the image but does not reboot talosctl upgrade --nodes 192.168.1.10 \ --image ghcr.io/siderolabs/installer:v1.7.0 \ --stage # The upgrade will be applied on the next reboot # You can trigger the reboot when ready ...

March 3, 2026 - When you upgrade your Talos cluster, also upgrade talosctl: # Download the matching version curl -sL https://github.com/siderolabs/talos/releases/download/v1.7.1/talosctl-linux-amd64 -o talosctl chmod +x talosctl sudo mv talosctl /usr/local/bin/

January 27, 2026 - # local powershell talosctl apply-config --insecure --file controlplane.yaml -n $IP -e $IP talosctl config merge ./talosconfig talosctl config context $CLUSTER talosctl config endpoint $IP talosctl config node $IP talosctl bootstrap talosctl upgrade --image factory.talos.dev/oracle-installer/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba:v1.12.2 # Will get stuck as shown below (Logs)

April 26, 2026 - apiVersion: tuppr.home-operations.com/v1alpha1 kind: KubernetesUpgrade metadata: name: kubernetes spec: kubernetes: # renovate: datasource=docker depName=ghcr.io/siderolabs/kubelet version: v1.36.2 # Required - target Kubernetes version # Optional - private registry for component images # (kube-apiserver, kube-controller-manager, kube-scheduler, kube-proxy, kubelet) # imageRepository: registry.example.com/k8s # Custom health checks (optional) healthChecks: - apiVersion: v1 kind: Node expr: status.conditions.exists(c, c.type == "Ready" && c.status == "True") timeout: 10m # Talosctl configuratio

March 3, 2026 - Sometimes you need a specific version of talosctl, particularly if your cluster is running an older version of Talos. The client and server versions should ideally match. # Install a specific version (replace v1.9.0 with your desired version) curl -LO https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-linux-amd64 chmod +x talosctl-linux-amd64 sudo mv talosctl-linux-amd64 /usr/local/bin/talosctl

Use this file to discover all available pages before exploring further. OS upgrades are effected by an API call, which can be sent via the talosctl CLI utility. The upgrade API call passes a node the installer image to use to perform the upgrade.

# Show all installable versions asdf list-all talosctl # Install specific version asdf install talosctl latest # Set a version globally (on your ~/.tool-versions file) asdf global talosctl latest # Now talosctl commands are available talosctl