-
Notifications
You must be signed in to change notification settings - Fork 216
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 events for pdb blocking deprovisioning #1849
Comments
/triage accepted |
/kind good-first-issue |
@jonathan-innis: The label(s) In response to this:
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. |
Can you show the configuration that you are using? As I'm reading it, it looks like we should block so long as the reason that the node is not eligible is that there is a PDB that is blocking so long as you don't have TGP set on your NodeClaim. |
/triage need-information |
@jonathan-innis: The label(s) In response to this:
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. |
/triage needs-information |
This issue has been inactive for 14 days. StaleBot will close this stale issue after 14 more days of inactivity. |
Description
What problem are you trying to solve?
Currently nothing tells drifted nodes are blocked by pdb. A feature like #224 but for pdb is very useful
How important is this feature to you?
The text was updated successfully, but these errors were encountered: