Closed figassis closed 3 years ago
That is not supported for now. I will add it in a future release. Can you make a concrete suggestion?
There might be another workaround for now but it is not tested. The controller virtual IP is added as SAN. But setting the controller virtual IP and the interface, that starts the internal load balancer. To prevent that the controller virtual IP interface has to be set to an empty string.
In the new version 2.4.0-beta.5 there are two new configuration options:
--san-dns-names string SAN DNS Names (comma separated)
--san-ip-addresses string SAN IP Addresses (comma separated)
Please let me know if that works for you.
Hi! yes, that'd definitely work, will test!
Did it work?
I'm running k8s-tew behind a load balancer external to the cluster, but I'm unable to point kubectl to the lb. My workaround is as follows:
server: https://node1:16443
Suffice to say this is not ideal. There are ways to add alternate names on kubeadmn setups. Is there a way using k8s-tew, or maybe this could be something to add as a command?
Thanks!