Hi Alex Could you please let me know the Kubernetes version and the cloudstack version you are using
Also did you try setting the global setting “endpoint.url” to the management server ip address http://<management-server-ip>:8080/client/api<http://%3cmanagement-server-ip%3e:8080/client/api> Regards Kiran From: Alex Crow <[email protected]> Date: Sunday, 10 November 2024 at 10:38 PM To: [email protected] <[email protected]> Subject: Re: Kubernetes service deployment questions On 10/11/2024 16:58, Alex Crow wrote: > > Hi All, > > > I'm just starting out with CloudStack, it looks brilliant, especially > in a new environment I've been dropped into. > > I've set up a lab for it with LINSTOR and NFS, and successfully > configured my Zone/Pod/Cluster with Advanced networking, and have run > various VMs with uploaded ISOs with no issue on both KVM and XCP-ng > hypervisors. > > However, while I can get a Kubernetes cluster up and showing as > started, when I go into the Kubernetes dashboard, although I can log > in with a token, I immediately receive the message: > > Unknown error (404) > the server could not find the requested resource (get > ingresses.extensions) > > I have tried deploying a LoadBalancer Service as described here: > https://docs.cloudstack.apache.org/en/latest/plugins/cloudstack-kubernetes-provider.html#deployment > > but, running: > kubectl apply -f > https://raw.githubusercontent.com/apache/cloudstack-kubernetes-provider/main/traefik-ingress-controller.yml > > Does not result in any new public IP address being created, and the > 404 error remains on accessing the dashboard. Also in the kubernetes > dashboard I can see, under services, a traefik service with a 2/3 > filled piechart icon next to the name, no green tick. It shows a > "Cluster IP" of 10.106.2.208, I'm not sure where that comes from, nor > the kubernetes service cluster IP of 10.96.0.1. > > Now, I could just be being an idiot as I'm new to k8s, only really > done standalone docker before, but I feel I'm missing something > somewhere or have made a mistake. > > Any help would be much appreciated! > > Thanks > > Alex > OK, just embarrassed myself again. I saw the error in the dashboard: Error syncing load balancer: failed to ensure load balancer: error retrieving load balancer rules: Get http://apachecloud:8080/client/api?apiKey=LTQI1W_OmNhwdloHiz8h6_kP4jzccQNPiVH7ACGd3scIyq4Oll66Hs4BdM7InvvtD2HaQ5FSWZEXsjXya9y59Q&command=listLoadBalancerRules&keyword=a274478c407ff4f8e88fe278a7c53d04&listall=true&response=json&signature=pyY9CBNpQurvn6ykyuwtkoBxUW0%3D: dial tcp: i/o timeout and realised that it should have been http://apachecloud1:8080 rather than http://apachcloud:8080, to match the endpoint in the cloudstack config. I will leave this here as a hint if anyone else comes across this! Thanks!
