This message was deleted.

Hey, currently vsphere is in experimental mode. We're actively testing it in combination with Kubeadm and RKE2 providers

So I have it so close to running. Or so it seems. But then it gets stuck in the WaitingForNodeRef state. In the capi logs I see E0815 144403.279715 1 controller.go:329] "Reconciler error" err="failed to create cluster accessor: error creating http client and mapper for remote cluster \"default/dev\": error creating client for remote cluster \"default/dev\": error getting rest mapping: failed to get API group resources: unable to retrieve the complete list of server APIs: v1: Get \"https://10.249.78.206:6443/api/v1?timeout=10s\": tls: failed to verify certificate: x509: certificate signed by unknown authority" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" ClusterResourceSet="default/dev-crs-0" namespace="default" name="dev-crs-0" reconcileID="c6bd1677-d613-4d3e-8702-8c07d4f193ac" I changed the capi-controller ca cert to be the same as the api-server cert thinking that might help. But still get that error.

@freezing-holiday-13112 What doc did you refer to?

Overall I've been using this document to setup turtle https://turtles.docs.rancher.com/getting-started/create-first-cluster/using_kubectl And uh...yeah so close to working. VM is created but I get this cert error

For comparison, I've got a non-prod cluster running on 3 RKE2 vms, cert-manager, Rancher, Turtles and CAPI Operator. vSphere API provider configured, but I'm about to reconfigure to use the RKE2 I see now that operator is throwing errors with clusterresourceSetBinding,