This message was deleted.
# terraform-provider-rancher2a
adamant-kite-43734
10/05/2023, 5:24 PMThis message was deleted.
g
gentle-evening-19566
10/09/2023, 4:15 PMYou can choose to not install the csi in this right? If you only want to have the SC marked as not default you can provide the storageClass.isdefault: false
b
busy-napkin-41956
10/09/2023, 4:17 PMI've not seen a hook that would prevent the csi chart from being installed. Can you link to / identify it?
busy-napkin-41956
10/09/2023, 4:19 PMin my solution, I absolutely do not want a CSI for vSphere storage installed at all, but I suppose I grabbed the first option I could find in the form of disabling the SC during install of the CSI.
g
gentle-evening-19566
10/09/2023, 4:22 PMIf it is already in your cluster you can just uninstall the helm chart (I think it is in the app catalog visible)
b
busy-napkin-41956
10/09/2023, 4:23 PMagreed, and i've taken that manual approach but it breaks with IAC methodology.
busy-napkin-41956
10/09/2023, 4:23 PMI'd rather handle it directly in the TF
g
gentle-evening-19566
10/09/2023, 4:24 PMYou selected the rancher-vsphere as cloud provider?
gentle-evening-19566
10/09/2023, 4:24 PMAs it then depends on how you configured your cluster initially
b
busy-napkin-41956
10/09/2023, 4:29 PMOk. so from this, I'm gathering that if I chose to host RKE2, built by Rancher, hosted on vSphere, through Terraform with Rancher2 provider, I should simply expect that an undesired Helm chart, vsphere-csi, will be installed and my best option is to try to obscure the chart and its functionality by disabling the storageClass?
g
gentle-evening-19566
10/09/2023, 4:45 PMIf you pick the defaults using RKE2 via Rancher hosted on vsphere you won’t get the csi installed. This is only done if you select rancher-vsphere as cloud provider and provide the specific vsphere and vSAN configuration as chart_values
gentle-evening-19566
10/09/2023, 4:46 PMAs long as you use the RKE2 cloud provider no vsphere components are installed
b
busy-napkin-41956
10/09/2023, 4:47 PMI think the disconnect here is, there is no manual creation of the cluster. TF and the Rancher2 provider. When the cloud provider was left as null, the config failed to create a cluster.
g
gentle-evening-19566
10/09/2023, 4:48 PME.g. this is an example of TF where you configure the csi directly when creating a cluster
https://github.com/frank-at-suse/vsphere_rancher_cluster
b
busy-napkin-41956
10/09/2023, 4:48 PMThank you, I'll review this and see if I can replicate in our environment. Appreciate your help!
g
gentle-evening-19566
10/09/2023, 4:52 PMWe use the option to leave the cloud-provider-name empty (“”). Which results in the default RKE2 provider using machine pools created as vsphere types. So I am sure it works. We deploy the csi manually afterwards.
b
busy-napkin-41956
10/09/2023, 4:53 PMThis is exactly what i want to achieve. Even Frank's repo sets the value to "rancher-vsphere" so if you're able to proceed with it set to empty, then I'll test that today.
g
gentle-evening-19566
10/09/2023, 4:54 PMYes you can leave it empty and then it just uses the RKE2 default provider (which is a bit more limited compared to the VMware cpi)
b
busy-napkin-41956
10/09/2023, 4:55 PMnoted. thank you
k
kind-air-74358
10/09/2023, 4:58 PMIf you need some more help, share some snippets and I can take a look
b
busy-napkin-41956
10/09/2023, 4:58 PMWill do. Thanks again