Feature max vol limits #214
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
tssushma
requested review from
bharadwajrs-dell,
boyamurthy,
delldubey,
mjsdell,
nidtara,
prablr79,
santhoshhs10,
SinuChacko,
shampavman and
shanmydell
as code owners
tssushma
force-pushed
the
feature_max_vol_limits
branch
from
854361b
to
540bc71
Compare
boyamurthy
approved these changes
Jul 25, 2023
tssushma
force-pushed
the
feature_max_vol_limits
branch
from
af848b4
to
f79d0c1
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.
Description
This feature helps in limiting the number of Volume per node by the user.
GitHub Issues
List the GitHub issues impacted by this PR:
dell/csm#878
Checklist:
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration
Output of the test confirming the volume limits per node
Events:
Type Reason Age From Message
Warning FailedScheduling 59s default-scheduler 0/2 nodes are available: 2 node(s) exceed max volume count. preemption: 0/2 nodes are available: 2 No preemption victims found for incoming pod.