GitHub user n4l5u0r created a discussion: Struggling on setting up the endpoint.url for Kubernetes clusters to have a Running state.
Hello I have a general questionning here regarding the managment of k8s clusters in Cloudstack. For security purpose and as designed too by Cloudstack recommendations I keep the Mgmt Network isolated. But when deploying a Kubernetes cluster I have to make Cloudstack being able to reach cluster endpoint by setting up the correct endpoint.url configuration. 4 questions here: - What to setup here as value to replace the standard `http://localhost:8080/client/api` as before launching a k8s cluster Cloudstack request to update this value ? - What are the network requirements to have this link operational once the new value of endpoint.url is set ? - Regarding security perspectives am I forced to have mgmt accessing public network ? - This endpoint.url is it generic ? what happens if I deploy a second k8s cluster ? How to manage this ? Sorry for all these questions I am kind of lost on this topic based on the existing documentation we have on the 4.20.2.0. My current setup: - Networks: - Mgmt : 10.10.0.0/20 - Storage: 10.20.0.0/20 - Guest: 10.30.0.0/20 - Public: 10.40.0.0/20 - Servers: - 2 Mgmt servers - (networks : mgmt + storage) - 3 KVM servers - (networks: mgmt + storage + guest-bridge + public) - k8s cluster deployed in an isolated guest network. - everything runs fine one the cluster except the Running state never achieved in the Cloudstack UI so the endpoint remains null at k8s cluster definition in Cloudstack database: ```yaml ... "domainid": "e5d0db71-bd78-11f0-97ba-d4ae52cfd8f3", "domainpath": "/", "endpoint": "", "hasannotations": false, "id": "6d06e382-172e-4a2f-ac33-dde8d04b0e3c", "ipaddress": "10.40.0.13", ... ``` Thank you very much 🙏 GitHub link: https://github.com/apache/cloudstack/discussions/12037 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
