GitHub user hodie-aurora added a comment to the discussion: HA Kubernetes Cluster Not Using Auto-Generated Public IP in Apache CloudStack 4.21.0.0
@weizhouapache Following up on my previous comment, I believe that using kubectl --insecure-skip-tls-verify=true only allows symptomatic access to the cluster but doesn't resolve the root cause. The fundamental issue appears to be that during cluster initialization, the Kubernetes API server is configured to point to the internal IP of a single control node VM (e.g., 10.1.0.219:6443) instead of the auto-generated public IP. If the cluster were properly set up to use the public IP (with the load balancer), the kubectl access problems would be resolved naturally, and the cluster would truly achieve high availability—meaning it could tolerate the failure of any number of control nodes up to less than half without the entire cluster going down. Is my understanding of the root cause correct? Thank you for any confirmation or additional insights! GitHub link: https://github.com/apache/cloudstack/discussions/11642#discussioncomment-14422607 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
