exclude cordoned nodes while scheduling #26
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
abhilashshetty04
changed the title
abhilashshetty04
changed the title
Signed-off-by: Abhilash Shetty <[email protected]>
abhilashshetty04
force-pushed
the
exclude_cordoned_node
branch
from
3df5763 to
d2a4222
Compare
1 task
Abhinandan-Purkait
approved these changes
Feb 18, 2025
tiagolobocastro
approved these changes
Feb 18, 2025
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 this PR does:
This PR adds a check in scheduler to filter cordoned k8s node. For localpv, we should not schedule volume cr(lvmvolume, zfsvolume) on cordoned node as App will not be scedulable there. Pod gets stuck in
PendingWhich issue(s) this PR fixes:
openebs/lvm-localpv#366