Support multi-tenancy in access zone networks#432
Merged
Conversation
Co-authored-by: Don Khan <don.khan@dell.com>
Co-authored-by: Alexander Hoppe <Alexander.Hoppe@dell.com>
Co-authored-by: Oliver Chen <oliver.chen1@dell.com>
Co-authored-by: Don Khan <don.khan@dell.com>
8 tasks
donatwork
previously approved these changes
Aug 15, 2025
Contributor
Merging this branch will not change overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
donatwork
approved these changes
Aug 18, 2025
EvgenyUglov
approved these changes
Aug 18, 2025
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
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
Add the ability to support multiple tenants by allowing for storage classes to specify an access zone which will be used to match nodes and networks in the access zone. On driver startup the nodes will be labelled with entries aligning with the networks and IP addresses, for example:
csi-isilon.dellemc.com/aznetwork-192.168.100.0-24-192.168.100.10=true
During CreateVolume the storage class will contain the new field for specifying the access zone and that value will override the value in the driver's configuration.
GitHub Issues
List the GitHub issues impacted by this PR:
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