You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are use cases where it's not only safe, but required to mount a CSI in RW Many mode. Yes, in general this is a dangerous plan if you don't know what you're doing. But for synchronized workloads including (but not limited to) Kubevirt VM migration it's necessary.
Describe the solution you'd like
Add an option to enable Multi Node access, this would include:
Providing the ability for a user to enable/disable via a Storage Class Parameter (default would be disabled and leave the current attach restrictions unchanged)
Add the multi node capabilities to the plugin (RO perhaps should be separated)
Modify the plugin to permit additional connections if the volume has a multi access mode set
Describe alternatives you've considered
Rather than relying on the Storage Class, I considered adding a flag to the plugin to enable multi node access during start up. This still might be a good approach, but it seemed like providing multiple SCs for a single plugin was more user friendly, and safer because it would require explicit requests for multi node access in two forms (an multi no access SC, and the access-mode settings on the PVC).
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
There are use cases where it's not only safe, but required to mount a CSI in RW Many mode. Yes, in general this is a dangerous plan if you don't know what you're doing. But for synchronized workloads including (but not limited to) Kubevirt VM migration it's necessary.
Describe the solution you'd like
Add an option to enable Multi Node access, this would include:
Describe alternatives you've considered
Rather than relying on the Storage Class, I considered adding a flag to the plugin to enable multi node access during start up. This still might be a good approach, but it seemed like providing multiple SCs for a single plugin was more user friendly, and safer because it would require explicit requests for multi node access in two forms (an multi no access SC, and the access-mode settings on the PVC).
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: