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

docs: improve talos kubernetes upgrade note

Browse Source 
Improve working on Talos upgrade vs Kubernetes upgrades.

Signed-off-by: Tim Jones <tim.jones@siderolabs.com>
This commit is contained in:
Tim Jones 2022-07-15 15:04:14 +02:00
parent 88bb017ed0
commit 014b85fdcb
No known key found for this signature in database
GPG Key ID: A2A702DD5B689F45
3 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -20,7 +20,9 @@ This will simply update the boot reference and reboot.
Unless explicitly told to `preserve` data, an upgrade will cause the node to wipe the [EPHEMERAL]({{< relref "../learn-more/architecture/#file-system-partitions" >}}) partition, remove itself from the etcd cluster (if it is a control node), and generally make itself as pristine as is possible.
(This is generally the desired behavior, except in specialised use cases such as single-node clusters.)
*Note* that unless the Kubernetes version has been specified in the machine config, an upgrade of the Talos Linux OS will also apply an upgrade of the Kubernetes version.
*Note* that the default since Talos version 1.0 is to specify the Kubernetes version in the machine config.
This means an upgrade of the Talos Linux OS will not apply an upgrade of the Kubernetes version by default.
Kubernetes upgrades should be managed separately per [upgrading kubernetes]({{ relref "../kubernetes-guides/upgrading-kubernetes" }}).
Each release of Talos Linux includes the latest stable Kubernetes version by default.
## Video Walkthrough

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

@ -20,7 +20,9 @@ This will simply update the boot reference and reboot.
Unless explicitly told to `preserve` data, an upgrade will cause the node to wipe the [EPHEMERAL]({{< relref "../learn-more/architecture/#file-system-partitions" >}}) partition, remove itself from the etcd cluster (if it is a control node), and generally make itself as pristine as is possible.
(This is generally the desired behavior, except in specialised use cases such as single-node clusters.)
*Note* that unless the Kubernetes version has been specified in the machine config, an upgrade of the Talos Linux OS will also apply an upgrade of the Kubernetes version.
*Note* that the default since Talos version 1.0 is to specify the Kubernetes version in the machine config.
This means an upgrade of the Talos Linux OS will not apply an upgrade of the Kubernetes version by default.
Kubernetes upgrades should be managed separately per [upgrading kubernetes]({{ relref "../kubernetes-guides/upgrading-kubernetes" }}).
Each release of Talos Linux includes the latest stable Kubernetes version by default.
## Video Walkthrough

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

@ -20,7 +20,9 @@ This will simply update the boot reference and reboot.
Unless explicitly told to `preserve` data, an upgrade will cause the node to wipe the [EPHEMERAL]({{< relref "../learn-more/architecture/#file-system-partitions" >}}) partition, remove itself from the etcd cluster (if it is a control node), and generally make itself as pristine as is possible.
(This is generally the desired behavior, except in specialised use cases such as single-node clusters.)
*Note* that unless the Kubernetes version has been specified in the machine config, an upgrade of the Talos Linux OS will also apply an upgrade of the Kubernetes version.
*Note* that the default since Talos version 1.0 is to specify the Kubernetes version in the machine config.
This means an upgrade of the Talos Linux OS will not apply an upgrade of the Kubernetes version by default.
Kubernetes upgrades should be managed separately per [upgrading kubernetes]({{ relref "../kubernetes-guides/upgrading-kubernetes" }}).
Each release of Talos Linux includes the latest stable Kubernetes version by default.
## Video Walkthrough