Repository navigation
Unable to launch CKS cluster on 4.22 build with vmware 8 #11831
Description
problem
Unable to launch CKS cluster on 4.22 build with vmware 8
versions
ACS 4.22 nightly build
Vmware 8.0
The steps to reproduce the bug
- Launch a cks cluster on the nightly build
- Cluster struck in starting state
- Login to the control node and check the deamon log
Logs
/var/log/daemonlog
10 12:15:53 systemvm kubelet[1923]: E1010 12:15:53.617514 1923 certificate_manager.go:596] "Failed while requesting a signed certificate from the control plane" err="cannot create certificate signing request: Post \"https://10.1.1.111:6443/apis/certificates.k8s.io/v1/certificatesigningrequests\": dial tcp 10.1.1.111:6443: connect: connection refused" logger="kubernetes.io/kube-apiserver-client-kubelet.UnhandledError"
What to do about it?
CKS cluster should start successfully
Activity
kiranchavala commentedon Oct 13, 2025
No issue observed with the 4.21 build and vmware 8
weizhouapache commentedon Oct 14, 2025
we are checking if #11823 fixes this issue
weizhouapache commentedon Oct 15, 2025
@kiranchavala
can you verify if it works with new systemvm template ?
DaanHoogland commentedon Oct 30, 2025
@kiranchavala , closing as outdated. please re-open if needed.
weizhouapache commentedon Oct 30, 2025
yes, it seems #11823 has fixed it already.
no issues found in testings on 4.22.0.0-RC with vmware 8.0
vladuntu commentedon Jan 6, 2026
Please check if Calico network does not conflict with your public IPs network.
If your public IP network is 192.168.0.0/16 then the cloudstack API is not accesible from the CKS cluster.
If that is the case then, run the command with your cluster config:
and edit
to an address that does not conflict with your public IP address (like 10.244.0.0/16) network and especially the IP address of your cloustack management server.