From f2b258b3733a8fcc34bccde3bf01855a512d519a Mon Sep 17 00:00:00 2001 From: Alex Corcoles Date: Tue, 30 May 2023 22:13:03 +0200 Subject: [PATCH] docs: document talosctl version for upgrades Use same version as running cluster. Signed-off-by: Alex Corcoles Signed-off-by: Andrey Smirnov --- website/content/v1.5/talos-guides/upgrading-talos.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/content/v1.5/talos-guides/upgrading-talos.md b/website/content/v1.5/talos-guides/upgrading-talos.md index 8ab9694b2..b39756c47 100644 --- a/website/content/v1.5/talos-guides/upgrading-talos.md +++ b/website/content/v1.5/talos-guides/upgrading-talos.md @@ -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.