High Risk Operation

KubeSphere supports high availability of master and working nodes to ensure cluster stability, based on the underlying kubernetes scheduling mechanism to ensure the sustainability and stability. It is not recommended to shut down or restart nodes for no reason, because such operations are high-risk operations may cause the service is not available, please operate with caution. High-risk operations are supposed to inform users about the risks in advance, the engineer is only allowed to implement the backend operation after users and other engineers agree. For example, be aware of the following list describes high-risk and prohibited operations that may cause a node or cluster unavailable:

High-risk Operations

SequenceHigh-risk Operation
1Restart the cluster node or reinstall the operating system.
2It is recommended that you do not install additional software on the cluster node, which could make the cluster node unavailable.

Prohibitive Operations

SequenceProhibitive Operations
1Delete /var/lib/etcd/. Delete /var/lib/docker. Delete /etc/kubernetes/. Delete /etc/kubesphere/
2Disk formatting, partitioning.