https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
h
Yes.
It will use the harvester storageclass provided by the Harvester CPI you can see it uses when deploying a cluster. It will consume from the same StorageClass you created the VM Image.
q
@happy-cat-90847 if that's the case, should i see separate pvc's spin up in longhorn when i create the deployment via rancher? sorry, i planned on testing this my self, but i'm having stability issues with a nested harvester cluster i setup for testing.
h
Yes. You won’t see new volumes for images but will for VMs and Kubernetes CSI PV requested
q
so i'm fairly new to k8s, just to clarify, when you say i will for vms and k8s csi pv requested. for example if i deploy a mysql server w/ a pvc declared, i should see that pvc created in longhorn. am i catching that right?
👍 1
everything i've done in k8s is either base-metal, or local storage, so still trying to get my bearings on cloud setups (but on bare metal)
perfect, thank you!
@happy-cat-90847 quick follow up. it seems when creating the cluster with rancher (via internal harvester) when i provision pvc's they all are landing on the Longhorn SC. i created and set to default an SSD SC. but it looks like there's no way to get rancher to use that. any pointers to get the pvcs to land on the proper SSD SC?
h
You need to add it by hand. That is a new feature that lands on 1.1.1
You are on the correct path. I also look forward to this. But as we talk about quotas, people consuming SCs and at scale, there is a lot of code that needs to be written. In order to simplify this, we can just have the operator add the SC
q
do you have anything on adding it by hand? the only way i've been able to move PVCs from one SC to another has been to use DD. not sure how i'd do that w/ it being all done internally w/ harvester / rancher.
i dont mind doing it by hand for now, i guess i'm just not totally sure what the manual workaround is.
2 Views
Open in Slack
PreviousNext
Powered by