Question
Answer
To resolve the 'waiting for cluster agent to connect' error when deploying a k3s cluster on vSphere using Rancher, you may need to deploy the vSphere cloud provider. The provider is bundled with RKE1 and RKE2 but not k3s. Check out the documentation on how to deploy Kubernetes on vSphere with Helm at https://github.com/kubernetes/cloud-provider-vsphere/blob/master/docs/book/tutorials/kubernetes-on-vsphere-with-helm.md for more information.
creamy-room-58344
12/02/2022, 9:07 PMwaiting for cluster agent to connect
Rancher v2.7.0
Machine Provider: VMware vSphere
Kubernetes version: v1.24.8+k3s+1
pool1: 3 master+etcd nodes
pool2: 4 worker nodes
Nodes image: Ubuntu Cloud 22.04 (same as used in RKE1 and RKE2)
Conditions shows:
Ready False 2.7 hours ago [Disconnected] Cluster agent is not connected
Reconciling True 2.7 hours ago [Reconciling]
RKECluster True 2.6 hours ago —
SecretsMigrated True 2.7 hours ago —
ServiceAccountSecretsMigrated True 2.7 hours ago —
Stalled False 2.7 hours ago —
SystemProjectCreated True 2.7 hours ago —
Updated Unknown 2.6 hours ago [Waiting] configuring bootstrap node(s) k3s-lab01-master-789d65b648-fxft7: waiting for cluster agent to connect
I'm able to deploy RKE1 and RKE2 clusters
What other info can I provide to help solve this issue?creamy-pencil-82913
12/02/2022, 9:33 PMcreamy-room-58344
12/02/2022, 10:28 PMcreamy-pencil-82913
12/02/2022, 10:44 PM