This message was deleted.
# harvester
a
This message was deleted.
t
The only tricking part is setting up multipathd. I wrote a guide for that and installing Pure’s CSI - https://github.com/clemenko/px-harvester I would HIGHLY recommend using a 3rd party CSI. 😄 Full disclosure, I work for a storage company.
h
so it turns out seagate provides a CSI for the SAN in question. I'm thinking that should be my best bet? https://github.com/Seagate/seagate-exos-x-csi
t
I would try that CSI. I am not a fan of the generic.
h
That's fair, is there even a generic iSCSI CSI? I didn't see one looking through the documentation but I'm new to harvester so maybe I missed it. Either way the seagate provided one comes with a multipath config as well so it seems like it might be the most straight forward. Thanks for the info
t
Not sure. I would use the storage vendors.
h
fair enough, will do
g
you should be able to use iscsi directly.. i think i did it a while back and now have forgotten what i did
t
without a CSI? manual commands?
g
i am sure i did something when i was adding iscsi support..
in PV spec you under PersistentVolumeSource
i pointed directly to the iscsi tgt and lun using this and mounted it in a vm
t
Ah. the csi makes it easier to build/connect to the lun.
👍 1
g
hopefully this helps
a
Of note, the Harvester Knowledge Base documents also have a few iSCSI examples, including: https://harvesterhci.io/kb/install_netapp_trident_csi
h
I did see that but I'm not using netapp, I will check out the manual iSCSI stuff, especially if I have issues with the official CSI I found
one related question, the CSI I found is RWO only, which I understand means no live migration, VM HA should still work correct? Since that's basically a cold migration