https://rancher.com/ logo
#vsphere
Title
# vsphere
a

adamant-kite-43734

12/15/2022, 1:14 PM
This message was deleted.
c

creamy-room-58344

12/15/2022, 9:37 PM
Hello there! To help debug, I would go into the VM and see if there is anything wrong with it I had the same issue cause the nodes weren't getting an IP address Also, if you are using cloud-init, check if everything you configured in it was applied
m

mammoth-vegetable-85565

12/15/2022, 10:53 PM
we can login to the vm's with ip ( we have dhcp ) and cloud-init is working as well ( we can see sample userdata executed when VM is booted )
f

few-spoon-45426

12/17/2022, 12:01 AM
hello, I'm having the same problem
I've checked and there is a problem with the rancher-vsphere-cpi-cloud-controller-manager
it's not configured and doesn't start
thus the nodes remain tainted and k8s is stuck
if I manually delete the vsphere CPI and CSI deployments then the cluster is bootstrapped
sadly the rancher-vsphere-cpi-cloud-controller-manager pod goes in crashloop because it is not configured correctly
h

hundreds-jackal-3140

01/02/2023, 8:14 PM
I am looking to replace my RKEv1 cluster with an RKEv2 cluster. Did you manage to fix this?
5 Views