Maybe just a documentation clarification question:...
# harvester
w
Maybe just a documentation clarification question: The Third-Party Storage Support (https://docs.harvesterhci.io/v1.5/advanced/csidriver/) section makes it seem like we can change the csi-driver-config to add or use Longhorn V2 Data Engine as the default. We have enabled the v2 engine, etc, on Harvester 1.5.1. We have created storage classes with Longhorn V2 CSI as the provisioner. But we are unable to change the
csi-driver-config
to select that (the fields as well as
Add
are disabled). Maybe it's not possible to make this change (yet probably because vm snapshots are not possible yet)? Maybe by enabling the v2 driver in general it -just happens-?
a
On the Storage Classes screen, if you set your LHv2 storage class as the default (rather than harvester-longhorn), then any images, volumes, etc. you create after that will default to using that storage class, and thus the LHv2 data engine
w
Ah ok I do see that now. That seems really obvious now and makes a lot of sense. Thank you!
a
no problemo 🙂
(I can't remember whether or not that's explicitly called out in the docs, so there may well be room for improvement there)
w
I just went back and looked through it and it looks like it's not quite there. • https://docs.harvesterhci.io/v1.5/advanced/longhorn-v2 mentions adding the longhorn v2 storage driver, but falls short of instructions on switching the default driver via that screen - but that could be necessary/intentional to leave that out at this stage of implementation, because maybe v2 for root volumes isn't recommended. • https://docs.harvesterhci.io/v1.5/advanced/csidriver directs users to the csi-driver-config screen specifically, and the volume configuration for the VMs, but never mentions the Advanced -> Storage Classes screen, so it may be unintentionally misleading.
a
Thanks for checking -- v2 wasn't possible for root volumes when https://docs.harvesterhci.io/v1.5/advanced/longhorn-v2https://docs.harvesterhci.io/v1.5/advanced/longhorn-v2 was originally written for Harvester v1.4, so didn't make sense to set that as a default then. You're right, we should call this out somewhere though, probably in https://docs.harvesterhci.io/v1.5/advanced/csidriver/ because that's applicable to other storage providers too.
I'll open a docs issue
w
Sounds great thanks!
One last related question I have there, is I found the documentation for adding the Host Storage Class to a cluster that uses the Harvester provider. https://docs.harvesterhci.io/v1.5/rancher/csi-driver#deploying-1. I'm wondering if there is a way coming, in the roadmap, to add or select storage classes during the cluster creation process. It's probably possible using Additional Manifest, but wanted to see if it was on the radar. Thanks!