[Bug]: Failed to create tkc from pre installed supervisor

Holorouter Version

9.0.2

VCF Version

VCF 9.0.2.0

Target Type

vCenter Cluster

Describe the bug

I successfully deployed the VCF9 family bucket using Holodeck 9.0.2.0, but there was a problem when creating the TKC cluster with the deployed supervisor using Holodeck. I think it may be due to communication issues between the supervisor VPC network and the TKC VPC network, but after checking the VPC configuration of nsx-t, I still couldn't find the problem.
TKC's CP virtual machine did not obtain an IP address.

Reproduction steps

1. create namespace
   2.assign storage policy
   3.assign content library(photon-5-amd64-v1.35.2---vmware.1-vkr.3) and vm classs
   4.kubectl apply -f tkc-name.yaml
   5.kubectl describe tkc-name

Expected behavior

2026-04-16T03:07:30Z
Addon DNS is not ready: unable to reconcile kubeadm ConfigMap's CoreDNS info: unable to retrieve kubeadm Configmap from the guest cluster: failed to get server groups: Get "https: //10. 1.0. 8: 6443/api?timeout=10s": net/http: request canceled while waiting for connection (Client. Timeout exceeded while awaiting headers) , Addon KubeProxy is not ready: unable to retrieve kube-proxy daemonset from the guest cluster: failed to get server groups: Get "https://10.1.0.8:6443/api?timeout=10s": net/http: request canceled while waiting for connection (Client. Timeout exceeded while awaiting headers)

Relevant logs

Events:				
Type	Reason	Age	From	Message
Normal	Pending	6m40s	cluster-controller	VSphereMachineTemplate "t25/t25-cluster01-node-pool-01-7cr77"
Normal	TopologyCreate	6m39s	topology/cluster-controller	t25-cluster01 InfrastructureReady is now True
Normal	TopologyCreate	6m39s	topology/cluster-controller	Cluster t25-cluster01 is Pending
Normal	TopologyCreate	6m39s	topology/cluster-controller	Created VSphereCluster "t25/t25-cluster01-kwk6v"
Normal	TopologyUpdate	6m39s	topology/cluster-controller	Created VSphereMachineTemplate "t25/t25-cluster01-8p5pl"
Normal	TopologyCreate	6m39s	topology/cluster-controller	Created KubeadmControlPlane "t25/t25-cluster01-swlhl"
Normal	TopologyCreate	6m39s	topology/cluster-controller	Updated Cluster "t25/t25-cluster01"
Normal	Provisioning	6m39s	cluster-controller	Created
Normal	TopologyCreate	6m39s	topology/cluster-controller	Created KubeadmConfigTemplate "t25/t25-cluster01-node-pool-01-1mj49"
Normal	TopologyUpdate	6m37s	topology/cluster-controller	Cluster t25-cluster01 is Provisioning
Normal	InfrastructureReady	6m29s (x2 over 6m29s)	cluster-controller	Created MachineDeployment "t25/t25-cluster01-node-pool-01-88xzg"
Normal	Provisioned	(x2 over_6m29s)	cluster-controller	Updated KubeadmControlPlane "t25/t25-cluster01-swlhl"
		6m29s		Cluster Cluster t25-cluster01 is Provisioned

Additional context

No response

Start by reproducing the namespace, storage policy, content library, VM class, and TKC application steps, then compare the supervisor and TKC VPC configuration with the reported events. Done means the TKC control-plane VM receives an IP address and the DNS and KubeProxy addons become ready without connection timeouts.