Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The virtual node taint information is not updated properly #622

Open
rxy0210 opened this issue Jun 4, 2024 · 0 comments
Open

The virtual node taint information is not updated properly #622

rxy0210 opened this issue Jun 4, 2024 · 0 comments
Labels

Comments

@rxy0210
Copy link
Member

rxy0210 commented Jun 4, 2024

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:

  • Kosmos version:
  • Others:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant