This message was deleted.

set the cloud provider to external

Can we do that with the existing cluster then? Just update the yaml file to have that value?

I don’t think so. Cloud provider selection should not be changed once the cluster is up.

So do we need to delete and rebuild the clusters?

you can try switching it but I don’t think the cloud provider will be able to take over the existing nodes. They will all have the providerid set from the default one.

When building a cluster selecting cloud provider as either external or vsphere, there’s a bunch of nodes in pending status, that have reason FailedScheduling, 0/1 nodes are unavailable: 1 node had taint {node.cloudprovider.kubernetes.up/uninitialized:true} that the pod didn’t tolerate

Yes, that means that the cloud provider has not come up yet. If you pick external you are on your own to deploy and configure a cloud provider. If you pick vsphere then there should be a spot in the UI to place your vsphere cloud provider configuration, which would include the address and creds for your vsphere server.

Cool. Looks like there is a firewall block on our end connecting to vsphere. Will retest once we get that opened

Good morning. I ran into this issue aswell with Rancher 2.7.0/1. RKE2 cluster deploys happily without cloud provider, but when selecting vSphere and filling in the blanks, the Rancher agent wont' startup on the downstream cluster nodes because of the wrong taint, like describe here. Values from the vSphere CSI fields in Rancher don't seem to get passed to the helm chart that executes them, so it's a +1 for us.