[CAPV] Control plane Machine stuck in "WaitingForKubeadmInit" even though KubeadmConfig has DataSecretAvailable

[dhqanh-rcc]

The control plane machine is created successfully in vSphere and assigned an IP via InClusterIPPool, and the KubeadmConfig reports DataSecretAvailable=True, but the KubeadmControlPlane remains in WaitingForKubeadmInit state indefinitely.

Worker nodes cannot be created because they depend on a ready control plane.

In the capv-controller logs, I see the following message:
"Connect failed" err="error creating HTTP client and mapper: cluster is not reachable: Get \"[https://<IP_address>:6443/?timeout=5s\":](https://<IP_address>:6443/?timeout=5s\%22:) context deadline exceeded"

Environment:

Cluster-api-provider-vsphere version: 1.13.1
Kubernetes version: (use kubectl version):

Client Version: v1.33.0
Kustomize Version: v5.6.0
Server Version: v1.32.0

OS (e.g. from /etc/os-release): ubuntu-2204-kube-v1.31.0.ova

[chrischdi]

Please take a look at the control plane machine and provide the cloud-init logs.

That should contain the logs for kubeadm and show why kubeadm failed or does not even run.