Fatal problems caused by k3s should be paid attention to

[clcc2019]

Environmental Info:
K3s Version:
v1.29.4+k3s1

Node(s) CPU architecture, OS, and Version:
5.15.117-1.el8.x86_64

Cluster Configuration:

Describe the bug:

My node was NotReady after running for a while, and ssh could not connect to the node. I found that the network was damaged when I logged in through vnc. Finally, I uninstalled k3s and restored the network. I was able to connect to my instance after executing the iptables -F cleanup policy

Steps To Reproduce:

• Installed K3s:

Expected behavior:

Actual behavior:

Additional context / logs: