scheduler server add leader elect #196
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
lengrongfu
force-pushed
the
feat/add-leader-elect-param
branch
from
3c0ea1f to
a55741e
Compare
lengrongfu
force-pushed
the
feat/add-leader-elect-param
branch
from
a55741e to
c4556c9
Compare
|
@archlitchi @wawa0210 PTAL |
lengrongfu
force-pushed
the
feat/add-leader-elect-param
branch
from
c4556c9 to
0a85cbc
Compare
Signed-off-by: rongfu.leng <[email protected]>
lengrongfu
force-pushed
the
feat/add-leader-elect-param
branch
from
0a85cbc to
d472283
Compare
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.
Cureent kube-scheduler and scheduler-extender can't run more than one pod because they do not use leader election, This PR adds
leaderElectto controllerkube-schedulerandhami-schedulerservers, whether use leader election. default: use helm.Release.Namespacevalue to setleader-elect-resource-namespace.Fixes: #195
Test:
Start two scheduler pods; only one pod can execute the scheduler flow.
Start three use gpu pods that can running success.
