-
Notifications
You must be signed in to change notification settings - Fork 232
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
docs: add disruption controls design #516
Conversation
Pull Request Test Coverage Report for Build 6699985019
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great to see the progress on disruption controls!
Have just a few questions/thoughts on MaxUnavailable
Are you planning to be able to extend this to more mechanisms/controls with parameters, like "deprovision nodes if there are more than 20% over-allocation" or "more than 2 nodes of spare capacity"? |
The hope was that defining a |
Is this ready to merge? |
Fixes
Description
This is a request for comments on the disruption controls design.
Once this is implemented, it should solve the following:
spec.disruption.consolidateAfter
#735Please leave your comments!
How was this change tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.