-
Notifications
You must be signed in to change notification settings - Fork 669
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
Move maximum-pods-per-nodes-evicted logic under a single invocation #266
Conversation
@damemi @seanmalloy PTAL |
Integrating part of #161 as well. |
Also, if this PR gets merged first, #254 will need to be rebased. |
c1d5fbc
to
990c21a
Compare
990c21a
to
37fc1e7
Compare
Each strategy implements a test for checking if a maximum number of pods per node was already evicted. The test duplicates a code that can be put under a single invocation. Thus, reducing the number of arguments passed to each strategy given EvicPod call can encapsulate both the check and the invocation of the pod eviction itself.
37fc1e7
to
077b7f6
Compare
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
/assign @ravisantoshgudimetla @aveshagarwal |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aveshagarwal, ingvagabund The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Move maximum-pods-per-nodes-evicted logic under a single invocation
Each strategy implements a test for checking if a maximum number of pods per node was already evicted. The test duplicates a code that can be put under a single invocation. Thus, reducing the number of arguments passed to each strategy given EvictPod call can encapsulate both the check and the invocation of the pod eviction itself.