Budgets will consider nodes that are actively being deleted for any reason, and will only block Karpenter from disrupting nodes voluntarily through drift, emptiness, and consolidation. Note that NodePool Disruption Budgets do not prevent Karpenter from cleaning up expired or drifted nodes.
The question over here is that does nodepool disruption budget prevent drifted nodes from being removed or not ?
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
How can the docs be improved?
https://karpenter.sh/docs/concepts/disruption/#nodepool-disruption-budgets
The question over here is that does nodepool disruption budget prevent drifted nodes from being removed or not ?