fix(vm): propagate PV nodeAffinity to VM pod for correct scheduling#2127
Open
loktev-d wants to merge 8 commits intofeat/vm/hotplug-block-devices-via-specfrom
Open
fix(vm): propagate PV nodeAffinity to VM pod for correct scheduling#2127loktev-d wants to merge 8 commits intofeat/vm/hotplug-block-devices-via-specfrom
loktev-d wants to merge 8 commits intofeat/vm/hotplug-block-devices-via-specfrom
Conversation
loktev-d
force-pushed
the
fix/vm/pv-node-affinity-scheduling
branch
from
2507e6f to
0cb1e94
Compare
This reverts commit 68a6fde. Signed-off-by: Daniil Loktev <lokt.daniil@gmail.com>
loktev-d
force-pushed
the
fix/vm/pv-node-affinity-scheduling
branch
from
0cb1e94 to
4028c4c
Compare
Signed-off-by: Daniil Loktev <lokt.daniil@gmail.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Propagate PV nodeAffinity to the VM pod so the Kubernetes scheduler respects disk topology constraints when placing VMs.
PVNodeAffinityTermsin VM state: collects nodeAffinity from PVs backing all block devices (spec refs + attached VMBDAs). Computes the intersection across PVs using cross-product ofNodeSelectorTerms.ApplyPVNodeAffinityin KVVM builder: merges PV node selector terms into the KVVM pod template affinity, preserving existing VM/class affinity via cross-product.nodeaffinitypackageCrossProductTerms/IntersectTermslogic.Why do we need it, and what problem does it solve?
What is the expected result?
Checklist
Changelog entries