alt-orchestra/talos
1
0
Fork 0
Code Issues Pull Requests Actions 27 Packages Projects Releases Wiki Activity

docs: document talosctl version for upgrades

Browse Source 
Use same version as running cluster.

Signed-off-by: Alex Corcoles <alex@corcoles.net>
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
This commit is contained in:
Alex Corcoles 2023-05-30 22:13:03 +02:00 committed by Andrey Smirnov
parent a0773f783c
commit f2b258b373
No known key found for this signature in database
GPG Key ID: 7B26396447AB6DFD
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/content/v1.5/talos-guides/upgrading-talos.md
View File

@ -162,3 +162,7 @@ If running a single-node cluster, and you want to force an upgrade despite the l
Nothing prevents the user from sending near-simultaneous upgrades to each node of the cluster - and while Talos Linux and Kubernetes can generally deal with this situation, other components of the cluster may not be able to recover from more than one node rebooting at a time.
(e.g. any software that maintains a quorum or state across nodes, such as Rook/Ceph)
**Q.** Which version of `talosctl` should I use to update a cluster?
**A.** We recommend using the version that matches the current running version of the cluster.