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.

January 21, 2025 - In my homelab, I am comfortable blasting through upgrades with a for loop, so my upgrade command looks like this: for node in 11 12 13 21 22 23 31 32 33; do talosctl upgrade -n 10.0.50.$node --image factory.talos.dev/installer/88d1f7a5c4f1d3aba7df787c448c1d3d008ed29cfb34af53fa0df4336a56040b:v1.9.2 --preserve; done

March 3, 2026 - While talosctl upgrade updates the Talos operating system, talosctl upgrade-k8s handles upgrading the Kubernetes components - the API server, controller manager, scheduler, kubelet, and other Kubernetes-specific pieces.

January 24, 2025 - If issues persist, you can perform a manual upgrade using the following commands: ... talosctl -n ${CONTROL_NODE} patch mc --mode=no-reboot -p '[{"op": "replace", "path": "/cluster/apiServer/image", "value": "registry.k8s.io/kube-apiserver:v'${K8S_INTERIM2}'"}]' talosctl -n ${CONTROL_NODE} patch mc --mode=no-reboot -p '[{"op": "replace", "path": "/cluster/controllerManager/image", "value": "registry.k8s.io/kube-controller-manager:v'${K8S_INTERIM2}'"}]' talosctl -n ${CONTROL_NODE} patch mc --mode=no-reboot -p '[{"op": "replace", "path": "/cluster/scheduler/image", "value": "registry.k8s.io/kube-scheduler:v'${K8S_INTERIM2}'"}]' talosctl -n ${CONTROL_NODE} patch mc --mode=no-reboot -p '[{"op": "replace", "path": "/machine/kubelet/image", "value": "ghcr.io/siderolabs/kubelet:v'${K8S_INTERIM2}'"}]'

March 3, 2026 - Make sure the Talos version you are upgrading to supports the Kubernetes version you want to run: # Check current Kubernetes version kubectl version # 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 v1alpha1 --nodes 192.168.1.10 -o yaml \ | yq eval '.spec' - > cp-01-config-backup.yaml

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

March 3, 2026 - A practical walkthrough of upgrading Kubernetes on Talos Linux using talosctl, covering version compatibility, the upgrade process, and post-upgrade verification.

March 3, 2026 - 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

March 3, 2026 - Learn how to use talosctl upgrade to safely upgrade Talos Linux on your cluster nodes with a rolling upgrade strategy

March 3, 2026 - # Upgrade using the official installer image talosctl upgrade --nodes 192.168.1.10 \ --image ghcr.io/siderolabs/installer:v1.7.0 # After the upgrade, the node will be running the version # corresponding to the new installer image

November 20, 2024 - This image below shows some of those messages of pulling down the images and then later on some more info on the dry run process, my assumption is that there was nothing saying fail so we can proceed with the actual upgrade here. The next step was to actually perform that jump, minus the –dry-run command flag. This can be done on one node and the whole cluster will be checked against is again my understanding. talosctl --nodes 192.168.169.211 --endpoints 192.168.169.211 --talosconfig=talosconfig upgrade-k8s --to 1.28.6

July 31, 2024 - talosctl upgrade --preserve --nodes $TALOS_CP -e $TALOS_CP --image ghcr.io/siderolabs/installer:v1.6.8 talosctl upgrade --nodes $TALOS_W1 -e $TALOS_CP --image ghcr.io/siderolabs/installer:v1.6.8 talosctl upgrade --nodes $TALOS_W2 -e $TALOS_CP --image ghcr.io/siderolabs/installer:v1.6.8

April 18, 2022 - After upgrade, carry out a talosctl convert-k8s to move from the self-hosted control plane to static pods.

... This command acts as a simple wrapper for talosctl upgrade-k8s. It only requires one node to initiate the upgrade process, after which it uses Talos discovery to locate all other nodes and upgrade them in sequence.

We notice that the Job we have used in inlineManifest presents a challenge to the upgrade; a simple solution to that would be to edit the talos config and remove the problematic section. talosctl --talosconfig talosconfig --nodes 10.5.0.2 patch mc --patch @remove-inlinemanifests.json

March 3, 2026 - Talos generally supports upgrading one minor version at a time, so plan your path accordingly. You need a clear picture of what you are working with. Document the following for every node in your cluster: ... # Get cluster member info talosctl get members --nodes <node-ip> # Check installed extensions talosctl get extensions --nodes <node-ip> # Retrieve the current machine config talosctl get machineconfig --nodes <node-ip> -o yaml