-
Notifications
You must be signed in to change notification settings - Fork 4
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
Feature Request: UI Integration to Apply Taints automatically to Node Pools #28
Comments
Hi @joeldeteves 👋 While we don't have UI / control panel integration yet, it is possible to specify so-called persistent node pool taints through the API that have the very behavior you are describing. See also the Does that help you, or were you asking for UI integration in particular? |
Related: #3 |
UI integration would definitely make things easier. But regarding the option you showed me, is it possible to apply a persistent node pool taint to an existing node pool?
Nevermind, I see it under the update section as well! Thank you, |
Great! I'm happy to keep the issue open to publicly track UI integration. |
Here's how I did it in case anyone else is searching for a quick solution:
Using Docs on how to use Thanks again @timoreimann |
It would be nice if there were an option in the DO Control Panel to automatically apply a taint to any nodes that belong to a specific node pool - it could be added under the Node Pool settings:
This would help us better manage our clients some of whom need to stay on specific nodes.
Currently I am handling it by manually re-applying the taints if I need to recycle the nodes.
I suppose I could script it and execute a job periodically, but it would be nice if it was done at the DO level.
Thanks for your consideration,
The text was updated successfully, but these errors were encountered: