Difference between revisions of "Microk8s Upgrade Nodes"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
- https://microk8s.io/docs/upgrading | - https://microk8s.io/docs/upgrading | ||
+ | |||
+ | Reckless without draining | ||
+ | ``` | ||
+ | sudo apt -y autoremove | ||
+ | sudo apt -y update | ||
+ | sudo apt -y upgrade | ||
+ | |||
+ | sudo snap refresh microk8s --channel=1.27/stable | ||
+ | reboot | ||
+ | ``` | ||
On each node | On each node |
Latest revision as of 04:16, 16 July 2023
Reckless without draining
sudo apt -y autoremove sudo apt -y update sudo apt -y upgrade sudo snap refresh microk8s --channel=1.27/stable reboot
On each node
sudo microk8s.kubectl get nodes
sudo microk8s kubectl drain kub3 --ignore-daemonsets # --force --delete-emptydir-data
ssh kub3
sudo snap refresh microk8s --channel=1.23/stable
sudo microk8s.kubectl get nodes
If you want to update kernel
sudo apt update && sudo apt -y upgrade reboot
sudo microk8s kubectl uncordon k3
Hostpath
sudo microk8s disable ingress && sudo microk8s enable ingress
Bugs 1.24
azurefile mount dir needed to be added
mkdir /var/snap/microk8s/common/var/lib/kubelet/pods/add97db7-b51c-4434-9927-xxxxxxxxx/volumes/kubernetes.io~csi/#azure-storage#k8s-zabbix-smb#zabbix-server#zabbix-dev/mount