-
Notifications
You must be signed in to change notification settings - Fork 25
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 flag to keep node cordoned for reap failures #60
Add flag to keep node cordoned for reap failures #60
Conversation
3f3e0ab
to
c6b65f7
Compare
Signed-off-by: shailshah9 <shailshah9@gmail.com>
…koproj#59) Signed-off-by: Jonah Back <jonah@jonahback.com> Signed-off-by: shailshah9 <shailshah9@gmail.com>
c6b65f7
to
ee4431b
Compare
…shah9/governor into feature/ignoreDrainFailure
Codecov Report
@@ Coverage Diff @@
## master #60 +/- ##
==========================================
+ Coverage 60.00% 62.52% +2.52%
==========================================
Files 9 9
Lines 1425 1425
==========================================
+ Hits 855 891 +36
+ Misses 476 441 -35
+ Partials 94 93 -1
Continue to review full report at Codecov.
|
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.
LGTM
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.
LGTM
Signed-off-by: shailshah9 <shailshah9@gmail.com>
Signed-off-by: shailshah9 <shailshah9@gmail.com>
Signed-off-by: shailshah9 <shailshah9@gmail.com>
Signed-off-by: shailshah9 <shailshah9@gmail.com>
Signed-off-by: shaoxt <shaoxt@gmail.com>
If the node fails to drain or if the node-reaper fails because of Bad PDBs, the new flag ignore-failure would keep the node cordoned so that no new pods are scheduled on the bad node.