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

Add the ability to disable nodes from being tainted #72

Open
js185692 opened this issue Oct 7, 2024 · 0 comments
Open

Add the ability to disable nodes from being tainted #72

js185692 opened this issue Oct 7, 2024 · 0 comments

Comments

@js185692
Copy link

js185692 commented Oct 7, 2024

Goal

I would like to propose a new configuration option for the HA controller that would allow users to disable the tainting of nodes in a cluster, which doesn't currently seem possible. The resulting functionality should result in less disruption to workloads that do not use Piraeus.

Context

I have a Kubernetes cluster that is running numerous different workloads, the majority of which do not need distributed storage and, therefore, do not use Piraeus. I've found, on occasion, that when my LINSTOR cluster becomes unhealthy (for example; when it loses quorum) a taint is applied to some/all nodes in the cluster; preventing all workloads, regardless of if they utilise Piraeus, from being deployed.

Issue #23 provides some extra context on the node taint feature.

Proposed Solution

Implement the following option:

--disable-node-taint boolean    when set to true; node taints will not be applied (default false)   
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

1 participant