config: Add podAntiAffinity to default sample yaml. #371 #393
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
runkecheng
added
documentation
runkecheng
changed the title
|
Improve the issue #371 |
|
Using a new sample file may be better, if the default configuration of anti-affinity can be unable to deploy in the verification environment. |
+1 |
runkecheng
force-pushed
the
add_pod_antiaffinity_to_sample
branch
from
f239ae4 to
00f2d3a
Compare
zhl003
pushed a commit
to zhl003/radondb-mysql-kubernetes
that referenced
this pull request
Aug 17, 2022
…o_sample config: Add podAntiAffinity to default sample yaml. radondb#371
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.
What type of PR is this?
/documentation
/enhancement
Which issue(s) this PR fixes?
ref: #371
What this PR does?
Summary:
Add podAntiAffinity to default sample yaml.
Guarantee to schedule nodes to different physical machines
Special notes for your reviewer?