https://rancher.com/ logo
#rke2
Title
s

square-policeman-85866

01/05/2023, 5:22 PM
Hi we have built an rke2 v1.22.11+rke2r1 cluster on vsphere via the rancher UI, cloud provider was set at none. When we try to install the vsphere cpi via the apps->chart the rancher-vsphere-cpi-cloud-controller-manager pod throws an error that port 10258 is already in use. Any idea how to get past this issue?
c

creamy-pencil-82913

01/05/2023, 5:32 PM
set the cloud provider to external
s

square-policeman-85866

01/05/2023, 5:50 PM
Can we do that with the existing cluster then? Just update the yaml file to have that value?
c

creamy-pencil-82913

01/05/2023, 5:54 PM
I don’t think so. Cloud provider selection should not be changed once the cluster is up.
the nodes will have been initialized and have the providerid set from the built-in rke2 default cloud provider (which is what if you pick none)
s

square-policeman-85866

01/05/2023, 5:57 PM
So do we need to delete and rebuild the clusters?
c

creamy-pencil-82913

01/05/2023, 8:54 PM
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.
You might be able to switch it and then delete and re-add the nodes one by one if you want them owned by the new cloud provider
s

square-policeman-85866

01/06/2023, 10:50 AM
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
Just to add we are deploying this via the Rancher Management UI
c

creamy-pencil-82913

01/06/2023, 5:48 PM
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.
s

square-policeman-85866

01/09/2023, 9:45 AM
Cool. Looks like there is a firewall block on our end connecting to vsphere. Will retest once we get that opened
t

thankful-tailor-9849

01/26/2023, 9:54 AM
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.
@creamy-pencil-82913: I saw you also participated in this thread. Also setting the values in the additional config under the CSI config didn't do the trick for me. I'm pretty new to this, and adressing issues on Github. Could you tell me what I could do to contribute to a solution and to get this issue on a roadmap to be fixed?
We've chosen RKE1 because this issue was a showstopper for us.
39 Views