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

Bug: node is not reconciled if tainting operation failed #76

Open
kvaps opened this issue Nov 1, 2024 · 1 comment
Open

Bug: node is not reconciled if tainting operation failed #76

kvaps opened this issue Nov 1, 2024 · 1 comment

Comments

@kvaps
Copy link
Member

kvaps commented Nov 1, 2024

I1101 06:50:28.044916       1 agent.go:440] updating node taints
I1101 06:50:28.103291       1 agent.go:276] managing node taints failed: failed to update node taints: Operation cannot be fulfilled on nodes "srv1": the object has been modified; please apply your changes to the latest version and try again

This error is thrown here:

if err != nil {
return err
}

@kvaps kvaps changed the title Bug: node is not reconciled if taint failed Bug: node is not reconciled if tainting operation failed Nov 1, 2024
@WanzenBug
Copy link
Member

I guess this could be improved somehow. Ideally, we would not need to retry this, as we could use a proper merge patch, but when I last tried it, it did not work specifically for taints.

Even better would be to move away from tainting directly. One idea would be to have a webhook that either labels all workloads or all PVs with some general anti-affinity, and then only label the node, which should work without having to update the node directly.

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

No branches or pull requests

2 participants