feat: add pod-anti-affinity #21
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
waynerv
force-pushed
the
add-pod-anti-affinity
branch
from
570dbee
to
670d6c3
Compare
waynerv
force-pushed
the
add-pod-anti-affinity
branch
from
670d6c3
to
adcfa3b
Compare
|
resolve #9 |
waynerv
force-pushed
the
add-pod-anti-affinity
branch
2 times, most recently
from
1e2671d
to
d0912aa
Compare
Codecov Report
@@ Coverage Diff @@
## main #21 +/- ##
==========================================
- Coverage 11.76% 11.45% -0.31%
==========================================
Files 18 19 +1
Lines 1335 1370 +35
==========================================
Hits 157 157
- Misses 1168 1203 +35
Partials 10 10 |
Signed-off-by: Xie Wei <[email protected]>
waynerv
force-pushed
the
add-pod-anti-affinity
branch
from
d0912aa
to
b249f19
Compare
|
/lgtm |
shilinlee
approved these changes
Oct 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, optional affinity scheduling is enabled for pods: components of the same type are distributed as evenly as possible among all nodes.
If affinity configuration in CRD is enabled, it enforces compliance with affinity scheduling.