Hi all, my current setup has a master with a floating IP that is not visible on the master, so it was not added to the certificate while running "kubicctl init". I can connect to my kubernetes cluster from the outside, but only by ignoring all TLS security measures. Otherwise I end up with:

Unable to connect to the server: x509: certificate is valid for 10.96.0.1, privateIP_address_here, not floatingIP_address_here

I found out that kubeadm can use the "--apiserver-cert-extra-sans" parameter to add that. Is there currently a way to handover the additional IP address to kubicctl during "init"? I only found "--adv-addr= IP address the API Server will advertise on" in the kubicctl Readme, which does not fit (at least with my current state of knowledge...). Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537