A water-utility platform runs kubeadm on a dual-homed control-plane host and must make the API advertise on the correct NIC while including that address in the API server certificate. Which ClusterConfiguration approach should the admin use?

Picture the API like a storefront address on a two-street building—you have to put the right street on the sign and on the certificate, or half the town never finds the door. In kubeadm’s ClusterConfiguration, that means pointing advertiseAddress or controlPlaneEndpoint at the NIC you want, and listing needed names/IPs under apiServer.certSANs. Skipping SANs is how you get scary certificate mismatch errors later.