This message was deleted.
# rke2
a
This message was deleted.
h
Nevermind, I figured it out... difference was vsphere CPI driver. Cluster that shows External-IP has CPI/CSI drivers installed On second cluster where it was showing <none> it does not have those drivers installed (yet)
c
changing the cloud provider after install isn’t really supported, it will probably work but you might run in to a fair bit of oddness
the nodes get a label put on them that indicates what cloud-provider was in use when they joined the cluster, if you switch after the fact the new cloud provider won’t know what to do with the nodes that have the wrong cloud-provider id
h
Oh! In this case I had left the default, so went back and edited the YAML...:
I can delete the cluster and recreate it since it is new... and will set the cloud provider to vSphere during creation
c
that’s a better choice, if you can
h
thanks, I will recreate it.
forgive my ignorance here... In Rancher UI, during cluster creation I set the Cloud provider to vSphere. Now, in Add-on config, if I enter login info, that will be visible to anyone who has cluster owner role correct?
Or, If I set Cloud Provider to External and after cluster is created I can deploy CPI/CSI from Apps. Is that supported method?
c
no, you should select the cloud provider when creating the cluster, if it is one of the cloud providers that comes with RKE2
Only if there is no built-in cloud provider would you want to select External and then deploy it manually as an additional manifest
✔️ 1