kosmos-io / kosmos

The limitless expansion of Kubernetes. Make Kubernetes without boundaries
https://kosmos-io.github.io/website/
Apache License 2.0
182 stars 40 forks source link

The virtual node taint information is not updated properly #622

Open rxy0210 opened 1 month ago

rxy0210 commented 1 month ago

What happened: Virtual node 08 has a non-Kosmos unschedulable stain on it. After restarting clustertree, this stain will be removed. But about an hour later, clustertree repainted the taint. What you expected to happen: Remove this taint How to reproduce it (as minimally and precisely as possible): Adds a taint to the virtual node. Then restart clustertree. Then remove the taint. Anything else we need to know?: Problem locating: Update the taint code in node_resources_controller.go. clone.Spec.Taints = rootNode.Spec.Taints. The rootNode is passed in when the clustertree starts and is not updated. The taints information of the node will be refreshed to the taints snapshot taken at the time of startup. Environment: