GitHub user n4l5u0r added a comment to the discussion: Struggling on setting up the endpoint.url for Kubernetes clusters to have a Running state.
Hello @rajujith created a tunnel between the KVM hosting the VR and the mgmt server and having the VR reaching the Mgmt server IP port 8080: ```bash root@r-10-VM:~# curl -I http://10.40.0.7:8080/client/ HTTP/1.1 200 OK Last-Modified: Thu, 16 Oct 2025 10:51:38 GMT Content-Type: text/html Accept-Ranges: bytes Content-Length: 22989 ``` the cluster looks sain : ```bash cloud@test-control-19a6d0b97d3:~$ sudo -i root@test-control-19a6d0b97d3:~# kubectl get nodes NAME STATUS ROLES AGE VERSION test-control-19a6d0b97d3 Ready control-plane 26m v1.33.1 test-node-19a6d0bc59b Ready <none> 25m v1.33.1 root@test-control-19a6d0b97d3:~# kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system calico-kube-controllers-7bfdc5b57c-czkb2 1/1 Running 0 26m kube-system calico-node-5ghgz 1/1 Running 0 25m kube-system calico-node-xfkwd 1/1 Running 0 26m kube-system coredns-674b8bbfcf-mfp5c 1/1 Running 0 26m kube-system coredns-674b8bbfcf-z2n5d 1/1 Running 0 26m kube-system etcd-test-control-19a6d0b97d3 1/1 Running 0 26m kube-system kube-apiserver-test-control-19a6d0b97d3 1/1 Running 0 26m kube-system kube-controller-manager-test-control-19a6d0b97d3 1/1 Running 0 26m kube-system kube-proxy-t46dv 1/1 Running 0 25m kube-system kube-proxy-xj4mc 1/1 Running 0 26m kube-system kube-scheduler-test-control-19a6d0b97d3 1/1 Running 0 26m kubernetes-dashboard dashboard-metrics-scraper-5bd45c9dd6-t7tvb 1/1 Running 0 26m kubernetes-dashboard kubernetes-dashboard-687457b9bd-sck8x 1/1 Running 0 26m ``` and ```bash [root@kvm-host-1-dev ~]# curl -k https://10.40.0.13:6443/version { "major": "1", "minor": "33", "emulationMajor": "1", "emulationMinor": "33", "minCompatibilityMajor": "1", "minCompatibilityMinor": "32", "gitVersion": "v1.33.1", "gitCommit": "8adc0f041b8e7ad1d30e29cc59c6ae7a15e19828", "gitTreeState": "clean", "buildDate": "2025-05-15T08:19:08Z", "goVersion": "go1.24.2", "compiler": "gc", "platform": "linux/amd64" } ``` and the `endpoint.url` is set to `http://10.40.0.7:8080/client/api` Mgmt & kvm logs are very clean no error. But the k8s cluster remains in `Starting` state. Where can I look what is happening ? a specific pod ? GitHub link: https://github.com/apache/cloudstack/discussions/12037#discussioncomment-14922978 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
