fix: support multi-zone topology scheduling for persistent volumes #2743
+150
−42
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.
Fixes #2742
Description
Fixes volume topology scheduling to correctly handle multiple topology terms in PersistentVolumes and StorageClasses.
VolumeTopology.getRequirements()to returnNodeSelectorTermslices instead of flatNodeSelectorRequirementslices to preserve OR semantics across multiple topology termsgetStorageClassRequirements()to process all allowed topologies, not just the first onegetPersistentVolumeRequirements()to process all node selector terms, not just the first oneInject()methodHow was this change tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.