Hi Bharat, If you deploy a CKS cluster on an isolated network, please ensure the public Ips (which include the endpoint IP of the CKS cluster, and Load balancer IPs) are reachable from the management server. The management server configures the k8s nodes (controller/worker) via the port 2222-222x of endpoint IP.
If you deploy a CKS cluster on a shared network, Load balancer is not supported. If you create a K8s service with nodeport, you can access it by <k8s node IP>:<node port>. If clusterIP is used, to access the service, you need to run "kubectl port-forward" on the controller node. -Wei On Fri, Mar 1, 2024 at 7:08 AM Bharat Bhushan Saini <bharat.sa...@kloudspot.com.invalid> wrote: > Hi Wei, > > > > I deployed cloudstack 4.18.1 on ubuntu 22.04 LTS on a standalone server > with kvm,nfs consist. > > > > I already tested some vm’s on the cloudstack on a shared network with > untagged vlan because what IP range I have that was bridged with the > private n/w and natting is enabled on that. On shared n/w I am able to > access internet but in isolated or L2 config it can’t. > > > > As per your suggestion, I tried with create default k8s n/w and also > create a network which have the same config of default k8s n/w but I untag > the vlan in that n/w. Both was not working. > > On shared n/w I a able to spawn the cluster and also able to login with > key and also deploy an application but the containers was running on the > Cluster IP. > > > > Thanks and Regards, > > Bharat Saini > > > > [image: signature_2926674288] > > >
