can someone provide the steps to add Harvester CSI to a cust rancher-users #harvester

Title

quaint-alarm-7893

03/17/2023, 4:55 PM

can someone provide the steps to add Harvester CSI to a custom rancher cluster? looks like the helm chart is looking for cloud-config folder, and there should be a file cloud-provider-config in that folder. how can i generate that file? i know it's all done automatically if you create a cluster in rancher w/ harvester as a cloud provider, but i'm doing a custom cluster so i can add windows nodes.

@salmon-city-57654 any feedback on this? i noticed you were a contributor. ^

chilly-soccer-69887

03/20/2023, 9:30 AM

@quaint-alarm-7893 If I remember correctly I don't think Harvester CSI supports Windows👀

quaint-alarm-7893

03/20/2023, 4:28 PM

@chilly-soccer-69887 i dont need it to support windows volumes, or make nodes, i just need to be able to join a windows node to a rke2/k3s cluster for windows workloads. i can manually handle volumes for it if needed.

👀 1

salmon-city-57654

03/22/2023, 5:06 PM

Hi @quaint-alarm-7893, did you mean that you want to join a windows node to an existing rke2/k3s cluster as an agent node? If yes, maybe you could refer to this (https://docs.rke2.io/install/quickstart#windows-agent-worker-node-installation)? And for the rke2 cluster management questions, maybe you could find some help on #rke2

For the first question, the cloud-config, you can generate by this script (https://raw.githubusercontent.com/harvester/harvester-csi-driver/master/deploy/generate_addon_csi.sh). Also, we have the document PR (https://github.com/harvester/docs/pull/288) in review (for the propose manual deployment). You could also refer to this. Thanks!

quaint-alarm-7893

03/22/2023, 11:39 PM

I'll Try those resources @salmon-city-57654, Thanks!

@salmon-city-57654 i got the csi working, but the cloud-provider seems to have a cert issue. my harvester cluster uses a self-signed cert, any way to get around the error on the cloud-provider? node_controller.go:241] Error getting instance metadata for node addresses: Get "https://192.168.5.100/k8s/clusters/local/apis/kubevirt.io/v1/namespaces/k8s/virtualmachines/k3s-m1": x509: certificate signed by unknown authority

192.168.5.100 is my vip

btw, that writeup for rke quickstart on a windows node didnt seem to work either. it only added the rke2 service, not containerd or calico, which was relly odd. the custom cluster registration url seems to work fine, so i dont know why the method in the quickstart didnt work.

18 Views