K3s: Difference between revisions
→Upkeep: Stopping K3s and Token requiring reset |
→Stopping K3s: Syncing in multiple hosts |
||
| Line 230: | Line 230: | ||
Changing K3s token requires resetting cluster. | Changing K3s token requires resetting cluster. | ||
== Stopping K3s == | === Stopping K3s === | ||
Disabling K3s NixOS module won't stop K3s related dependencies, such as containerd or networking. For stopping everything, either run "k3s-killall.sh" script or reboot host. | Disabling K3s NixOS module won't stop K3s related dependencies, such as containerd or networking. For stopping everything, either run "k3s-killall.sh" script or reboot host. | ||
=== Syncing K3s in multiple hosts === | |||
Nix syncs hosts to `configuration.nix`, for triggering `nixos-rebuild switch` in multiple hosts, it is commonly used `ansible`, which enables automation of cluster provisioning, upgrade and reset. | |||
=== Cluster Reset === | === Cluster Reset === | ||