fix: add setownershipondynamicfilesystems flag to csi controller #2016
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.

TL;DR
Added a new CSI configuration option to set ownership on dynamically provisioned filesystems.
This will instruct the csi controller to set ownership of
weka/v2filesystems automatically to the user of the storageclass (when usingfilesystemGroupNameoption)What changed?
setOwnershipOnDynamicFilesystems(default: false) to the CSI driverCSI_SET_OWNERSHIP_ON_DYNAMIC_FILESYSTEMSto the manager container--setownershipondynamicfilesystemsflag when the option is enabled