-
Notifications
You must be signed in to change notification settings - Fork 113
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 support for node taints #91
Comments
@OperationalDev .. have a query on your issue. |
If you cannot schedule pods on a node, then you cannot use that capacity. In a perfect world, nodes should not be cordoned for an extended period of time, but in my scenario, nodes can be cordoned for a couple of days and this can lead to running out of capacity. |
I would like this feature as well: to be able to exclude tainted nodes. |
It would be nice if we could add support for node taints.
e.g. If a node has been cordoned and is set to no schedule/execute, it should be possible to exclude this.
e.g.
Now if we exclude cordoned nodes:
We can see have less capacity available than we thought.
The text was updated successfully, but these errors were encountered: