Making kubeconfig_server_address configurable would be helpful in a setup without a control plane loadbalancer but with a common hostname pointing to the IP addresses of all control plane nodes, as described here.
When using the IP address of the first control plane node as kubeconfig_server_address, as currently implemented, the cluster cannot be accessed using that kubeconfig in case the first node is down. However, the cluster would still be accessible if the kubeconfig contained the hostname pointing to the IP addresses of all control plane nodes.
Description
Making
kubeconfig_server_address
configurable would be helpful in a setup without a control plane loadbalancer but with a common hostname pointing to the IP addresses of all control plane nodes, as described here.When using the IP address of the first control plane node as
kubeconfig_server_address
, as currently implemented, the cluster cannot be accessed using that kubeconfig in case the first node is down. However, the cluster would still be accessible if the kubeconfig contained the hostname pointing to the IP addresses of all control plane nodes.