当集群安装了calico时，sealos移除节点需要额外清理/var/lib/calico/nodename || When calico is installed on the cluster, sealos removes the node and requires additional cleaning of /var/lib/calico/nodename

[seriousgong]

Sealos Version

5.1.1

How to reproduce the bug?

1、sealos 移除启动过calico的节点时会残留var/lib/calico目录；
2、节点更改ip以及hostname等信息在加回集群时，再次加入集群时，会导致calico短暂的分配非预期的ip，直到calico更新var/lib/calico/nodename
3、该场景分配出的ip会被calico-controllers认为pod的节点变更而标记为leak ip，等grace period后回收，造成ip泄漏。
4、重复以上步骤加入的节点会出现重复分配ip的情况，概率非常大。

What is the expected behavior?

No response

What do you see instead?

No response

Operating environment

- Sealos version:
- Docker version:
- Kubernetes version:
- Operating system:
- Runtime environment:
- Cluster size:
- Additional information:

Additional information

No response

---

Sealos Version

5.1.1

How to reproduce the bug?

1. When sealos removes a node that has started calico, the var/lib/calico directory will remain;
2. When a node changes its IP address, hostname and other information and adds it back to the cluster, calico will temporarily allocate an unexpected IP address until calico updates var/lib/calico/nodename.
3. The IP allocated in this scenario will be marked as leak IP by calico-controllers because the node of the pod has changed. It will be recycled after the grace period, causing IP leakage.
4. The nodes added by repeating the above steps will be assigned IP addresses repeatedly, and the probability is very high.

What is the expected behavior?

No response

What do you see instead?

No response

Operating environment

- Sealos version:
-Docker version:
- Kubernetes version:
- Operating system:
- Runtime environment:
- Cluster size:
-Additional information:

Additional information

No response