-
Notifications
You must be signed in to change notification settings - Fork 604
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
Schduler: MAXFILLUP strategy will spread vreplicas across multiple pods #8263
Schduler: MAXFILLUP strategy will spread vreplicas across multiple pods #8263
Conversation
the MAXFILLUP algorithm was using an affinity strategy, meaning that it would prioritize adding new vreplicas to pods with the same resources. However, the downside is that if one pod goes down or gets re-scheduled the entire resource would be down and not produce events. By spreading replicas across multiple real replicas we would guarantee better availability. Signed-off-by: Pierangelo Di Pilato <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pierDipi 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 |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8263 +/- ##
==========================================
- Coverage 66.57% 64.61% -1.96%
==========================================
Files 371 362 -9
Lines 18281 22226 +3945
==========================================
+ Hits 12170 14361 +2191
- Misses 5325 7113 +1788
+ Partials 786 752 -34 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Pierangelo Di Pilato <[email protected]>
Signed-off-by: Pierangelo Di Pilato <[email protected]>
…hat is placements Signed-off-by: Pierangelo Di Pilato <[email protected]>
Signed-off-by: Pierangelo Di Pilato <[email protected]>
Signed-off-by: Pierangelo Di Pilato <[email protected]>
Signed-off-by: Pierangelo Di Pilato <[email protected]>
Signed-off-by: Pierangelo Di Pilato <[email protected]>
/lgtm |
/cherry-pick release-1.15 |
/cherry-pick release-1.16 |
@pierDipi: new pull request created: #8290 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. |
@pierDipi: new pull request created: #8291 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. |
/cherry-pick release-1.14 |
@pierDipi: #8263 failed to apply on top of branch "release-1.14":
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. |
the MAXFILLUP algorithm was using an affinity strategy, meaning that it would prioritize adding new vreplicas to pods with the same resources.
However, the downside is that if one pod goes down or gets re-scheduled the entire resource would be down and not produce events. By spreading replicas across multiple real replicas we would guarantee better availability.
Remove configurable HA scheduler and fix reserved replicas logic.