container:kubernetes:k3s_update
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| container:kubernetes:k3s_update [2020/12/07 16:27] – created stone | container:kubernetes:k3s_update [2021/01/11 14:58] (current) – [Via Installations Script] stone | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Update vom K3s Cluster ====== | ====== Update vom K3s Cluster ====== | ||
| - | .... | + | Ein Upgrade ist im Grunde ganz einfach. \\ |
| + | Es gibt verschiedene Möglichkeiten | ||
| + | * Via Installations Script | ||
| + | * Voll Automatisch via - system-upgrade-controller | ||
| + | * Manuell | ||
| + | |||
| + | \\ | ||
| + | Aktuell gehe ich nur die Version via Installations Script und Manuell ein. \\ | ||
| + | Mir persönlich ist die manuelle Version lieber. Daher auch hier als erstes angeführt. | ||
| + | \\ | ||
| + | |||
| + | ===== Manuelles Upgrade ===== | ||
| + | Hier benötigt man keine Infos über die Parameter bei der Installation oder sonst etwas. \\ | ||
| + | |||
| + | |||
| + | ==== Download der neuen Version suchen ==== | ||
| + | [[https:// | ||
| + | \\ | ||
| + | |||
| + | ==== Backup der atkuellen Version ==== | ||
| + | < | ||
| + | cp -a / | ||
| + | </ | ||
| + | \\ | ||
| + | |||
| + | ==== Stoppen einer Node ==== | ||
| + | < | ||
| + | systemctl stop k3s* | ||
| + | / | ||
| + | systemctl status k3s* | ||
| + | </ | ||
| + | \\ | ||
| + | |||
| + | ==== Update einer Node ==== | ||
| + | < | ||
| + | cd / | ||
| + | wget -O k3s https:// | ||
| + | </ | ||
| + | \\ | ||
| + | |||
| + | ==== Starten einer Master Node ==== | ||
| + | < | ||
| + | systemctl start k3s.service | ||
| + | systemctl status k3s.service | ||
| + | </ | ||
| + | \\ | ||
| + | |||
| + | ==== Starten einer Worker Node ==== | ||
| + | < | ||
| + | systemctl start k3s-agent.service | ||
| + | systemctl status k3s-agent.service | ||
| + | </ | ||
| + | |||
| + | \\ | ||
| + | ---- | ||
| + | |||
| + | |||
| + | |||
| + | ===== Via Installations Script ===== | ||
| + | Es ist wichtig das man die Parameter vom installieren noch weiß da man diese hier wieder anwenden muss! \\ | ||
| + | Die Parameter vom Update werden wieder in den Scripten zum Starten von K3s übernommen. | ||
| + | \\ | ||
| + | Das Upgrade funktioniert genau wie eine Installation auch. | ||
| + | < | ||
| + | Beispiel: | ||
| + | curl -sfL https:// | ||
| + | </ | ||
| + | Hier sollten aber wie gesagt die Parameter von jeder Node bei der Installation berücksichtigt werden. | ||
| + | \\ | ||
| + | \\ | ||
| + | |||
| + | ==== Upgrade K3s Using the Installations Script - Master Node ==== | ||
| + | < | ||
| + | root@kube01: | ||
| + | NAME | ||
| + | kube01 | ||
| + | kube02 | ||
| + | kube03 | ||
| + | |||
| + | |||
| + | export INSTALL_K3S_EXEC=" | ||
| + | curl -sfL https:// | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | [INFO] | ||
| + | Created symlink / | ||
| + | [INFO] | ||
| + | |||
| + | |||
| + | root@kube01: | ||
| + | NAME | ||
| + | kube01 | ||
| + | kube02 | ||
| + | kube03 | ||
| + | </ | ||
| + | \\ | ||
| + | |||
| + | ==== Upgrade K3s Using the Installations Script - Slave Node ==== | ||
| + | < | ||
| + | curl -sfL https:// | ||
| + | |||
| + | |||
| + | </ | ||
container/kubernetes/k3s_update.1607358478.txt.gz · Last modified: by stone
