You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kube-VIP is currently configured as a the Service loadbalancer.
It can also be configured to provide a single API (Elastic IP) for the cluster using BGP to ensure that one of the available control-plane nodes receives API requests.
During kubeadm init, the EIP should be known because it will be used in the generated certs.
By enabling this feature:
users can continue to choose between kube-vip and metallb for services
users will consume an additional IP address
The text was updated successfully, but these errors were encountered:
Kube-VIP is currently configured as a the Service loadbalancer.
It can also be configured to provide a single API (Elastic IP) for the cluster using BGP to ensure that one of the available control-plane nodes receives API requests.
During kubeadm init, the EIP should be known because it will be used in the generated certs.
By enabling this feature:
The text was updated successfully, but these errors were encountered: