3 ms·
I wonder if the Linstor integration with Kubernetes got better. A few years back, the CSI driver was full bugs and you couldn't really use it from K8s alone, yo
by lukaslalinsky 4y ago
I wonder if the Linstor integration with Kubernetes got better. A few years back, the CSI driver was full bugs and you couldn't really use it from K8s alone, you had to use Linstor tools on the servers directly to get things unstuck or get orphaned volumes to actually get deleted.
- tbronchain 4y agoA lot better. A couple of years ago I could see volumes on Linstor getting completely stuck and unrecoverable whenever the network was getting busy or unstable. Nodes reboot were a nightmare too. Have a setup now with their Piraeus operator[1], Kubernetes >= 1.20, rancher and calico, and it seems to be very stable. XFS have been giving better results too. Still, better not to try too many reboot loops on the nodes. 1: https://github.com/piraeusdatastore/piraeus-operator/ https://github.com/piraeusdatastore/piraeus-operator/
- hardwaresofton 4y agoNote, kvaps actually wrote one of the LINSTOR operators (which is no longer maintained): https://github.com/kvaps/kube-linstor https://github.com/kvaps/kube-linstor
- kvaps 4y agoYeah, because I have joined to Piraeus project :)