Hi Stanley, i probably ran into the same issue on Cloudstack 4.17.0.1 and was not sure if it's an issue not beeing in 4.18 yet.
The instances are up and running, but the kubebernetes cluster deployment issued on the control node via kubeadm is failing. When logging in to the control node and checking the kubeadm logs or manually executing the bash script, which is executing kubeadm to deploy the cluster you will probably find the error CRI v1 runtime API is not implemented for endpoint "unix:///run/containerd/containerd.sock": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService and/or [ERROR CRI]: container runtime is not running What i tried unsuccessful so far - editing /etc/containerd/config.toml and adding a few tipps from google searches here and there - deleting /etc/containerd/config.toml - installing the more up to date version of containerd Unfortunately i couldn't find the time to fully troubleshoot the issue yet and went the easy way of using Kubernetes ISO v1.25 which works like a charm. Maybe someone with more insight to it found an easy solution? Best regards, Stephan > Stanley Burkee <stanley.bur...@gmail.com> hat am 02.05.2023 15:23 CEST > geschrieben: > > > Hi guys, > > We are trying to create a Kubernetes cluster v.1.26 in Cloudstack 4.18. The > controller & worker nodes are provisioned and show in a running state but > Kubernetes Cluster is stuck in the starting state. > > Thanks a lot in advance. > > > Regards > > Stanley
