Include Nodepool disruption budget information in the NodePool status

[cnmcavoy]

Description

What problem are you trying to solve?
As a cluster administrator, I want to configure my NodePools with disruption budgets that allow a certain percentage of nodes to be disrupted. However, it can be hard to tell what an appropriate value is for the disruption, or debug whether the disruption is being blocked by the budget.

I would like to see the number of nodeclaims allowed to be disrupted, and the nodeclaims currently disrupted in the NodePool status information.

How important is this feature to you?

• 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

[jonathan-innis]

+1 on this -- seems completely reasonable to me. Are you comfortable if there is a eventually consistent nature to this data (like 10-20s or something) -- mainly want to avoid slamming the apiserver as this number changes during disruption

[jonathan-innis]

/triage accepted

[jonathan-innis]

/priority important-longterm

[jonathan-innis]

/help

[k8s-ci-robot]

@jonathan-innis:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.