[Enhancment] Support for LVM-HA about csi-driver-lvm

[majst01]

We do not have any plans right now to support such a scenario. What use-cases do you have in mind. But we are open for pull requests.

[mersl]

Hey there,

I'd like to suggest a feature. Are there any plans to add LVM-HA/ClusteredLVM support? That would be incredibly useful as it opens the csi up for many more usecases!

Do you think about something like https://github.com/angeloxx/k8s-flexvolume-lvm ??
This was a flex volume driver, which did activate single LVs on a shared VG using sanlock. I did like that idea to have ie. one shared iSCSI or FC lun from some storage shared across multiple k8s nodes.
(Asuming, you can't use an provisioner for some reason like the provisioner must not be able to access the management interface of the underlaying storage for security reasons. So one would create a big LUN/shared disk and map it to multiple k8s nodes. LVM on top manages the activation of various LVs on the node/for the pod they are needed)

If this is was you meant, I second that idea ;-)

thanks!

[modzilla99]

I'd like to use it with ISCSI and or KVM since I can't really do replica 3 with Longhorn or any other CSI driver for that matter and with lvm ha I can just add another lun and be done with it. That way failover is quick and I don't have to wait for ages for the volumes to rebuild...

[LarsBingBong]

@modzilla99 - I'm curious, why can't you use Longhorn?

[modzilla99]

High latency, high load, slow writes and 3x space use. Didn't have the best experience with it in the past...

…

On Wed., Mar. 23, 2022, 15:48 LarsBingBong, ***@***.***> wrote: @modzilla99 <https://github.com/modzilla99> - I'm curious, why can't you use Longhorn? — Reply to this email directly, view it on GitHub <#62 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHVOKZFZ4CYXR2WJS6MVHO3VBMVNTANCNFSM5GIPT6TA> . You are receiving this because you were mentioned.Message ID: ***@***.***>