mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-27 13:38:07 +00:00
Explain killall script in K3s docs
This commit is contained in:
@@ -0,0 +1,16 @@
|
|||||||
|
---
|
||||||
|
title: The k3s-killall.sh script
|
||||||
|
weight: 4
|
||||||
|
---
|
||||||
|
|
||||||
|
To allow high availability during upgrades, the K3s containers continue running when the K3s service is stopped.
|
||||||
|
|
||||||
|
To stop all of the K3s containers and reset the containerd state, the `k3s-killall.sh` script can be used.
|
||||||
|
|
||||||
|
The killall script cleans up containers, K3s directories, and networking components while also removing the iptables chain with all the associated rules. The cluster data will not be deleted.
|
||||||
|
|
||||||
|
To run the killall script from a server node, run:
|
||||||
|
|
||||||
|
```
|
||||||
|
/usr/local/bin/k3s-killall.sh
|
||||||
|
```
|
||||||
@@ -5,6 +5,8 @@ weight: 61
|
|||||||
|
|
||||||
If you installed K3s using the installation script, a script to uninstall K3s was generated during installation.
|
If you installed K3s using the installation script, a script to uninstall K3s was generated during installation.
|
||||||
|
|
||||||
|
> Uninstalling K3s deletes the cluster data and all of the scripts. To restart the cluster with different installation options, re-run the installation script with different flags.
|
||||||
|
|
||||||
To uninstall K3s from a server node, run:
|
To uninstall K3s from a server node, run:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|||||||
Reference in New Issue
Block a user