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
@kiranchavala Thank you for your suggestion! While using kubectl --insecure-skip-tls-verify=true can help bypass the TLS certificate verification issue, it doesn't address the root problem. The Kubernetes cluster is still pointing to an internal control node IP (e.g., 10.1.0.219:6443) instead of the auto-generated public IP for the HA load balancer. This creates a single point of failure—if the control node with that internal IP goes down, the entire cluster becomes unavailable, which defeats the purpose of a high-availability setup. I appreciate your valuable input and look forward to any further insights or potential fixes to ensure the cluster uses the HA public IP correctly GitHub link: https://github.com/apache/cloudstack/discussions/11642#discussioncomment-14411734 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
