Control Plane Static IPs - gpillon/k4all GitHub Wiki
If static IPs are used for the control plane nodes in a Kubernetes cluster, it is essential to configure the DNS server manually to resolve the hostname of the control plane node(s). Alternatively, you can enable kube-vip to manage the control plane VIP (Virtual IP) and provide automatic resolution.
-
Manually configuring the DNS server involves adding an entry for the control plane hostname and IP address in your DNS server configuration. This ensures that all nodes in the cluster can resolve the control plane hostname(s) correctly.
-
(Preferred) Enabling kube-vip automates this process by managing a highly available virtual IP (VIP) for the control plane nodes and ensures seamless resolution and accessibility (you can enable kube-vip editing the config at startup, when installing bootstrap node).
Choose the approach that fits best with your environment and operational needs.
NOTE: as a temporary workaround, you can add static names in /etc/hosts
eg: echo "192.168.x.x kube-bootstrap-abcdef" >> /etc/hosts