This message was deleted.
# vspherea
adamant-kite-43734
12/15/2022, 1:14 PMThis message was deleted.
c
creamy-room-58344
12/15/2022, 9:37 PMHello 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 PMwe 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 AMhello, I'm having the same problem
few-spoon-45426
12/17/2022, 12:01 AMI've checked and there is a problem with the rancher-vsphere-cpi-cloud-controller-manager
few-spoon-45426
12/17/2022, 12:02 AMit's not configured and doesn't start
few-spoon-45426
12/17/2022, 12:03 AMthus the nodes remain tainted and k8s is stuck
few-spoon-45426
12/17/2022, 12:03 AMif I manually delete the vsphere CPI and CSI deployments then the cluster is bootstrapped
few-spoon-45426
12/17/2022, 12:04 AMsadly 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 PMI am looking to replace my RKEv1 cluster with an RKEv2 cluster.
Did you manage to fix this?
5 Views