If you are not setting any optional values, set : to enable the default values. If not set, Konvoy randomly picks a Virtual Router ID for you. You can also set .vrid to specify the Virtual Router ID used by Keepalived. If not set, Konvoy automatically detects the network interface to use based on the route to the VIP. You can set .interface to specify the network interface for the Keepalived VIP. This value is optional if it is already specified in inventory.yaml as part of _plane_endpoint. The IP address specified in is used for the Keepalived VIP. In the above example, only use 51 one time, and then choose another value for each additional cluster. NOTE: If you run multiple clusters on the same L2 network, you must specify a unique VRID value for each cluster to prevent network issues. The following example illustrates the Konvoy configuration to use if the reserved virtual IP address is 10.0.50.20: kind: ClusterConfigurationĬontrolPlaneEndpointOverride: '10.0.50.20:6443' If the virtual IP address shares an interface with the primary IP address of the interface, you must disable any IP or MAC spoofing from the infrastructure firewall. If the address is in a different subnet, you may need to configure appropriate routes to ensure connectivity with the virtual IP address. The configuration is complete if the virtual IP address is in the same subnet as the rest of the cluster nodes. from the computer that is used to deploy Kubernetes.

from all hosts specified in the inventory file.Identify and reserve a virtual IP (VIP) address in your networking infrastructure.Ĭonfigure your networking infrastructure so that the reserved virtual IP address is reachable: Konvoy uses Keepalived to maintain high availability of the control plane. VRRP provides high availability by ensuring that virtual IP is active as long as one of the participating machines is active. VRRP allows you to assign a virtual IP (VIP) to participating machines, where it is active only on one of the machines. It uses the Virtual Router Redundancy Protocol (VRRP) to provide high availability. Keepalived provides two main functions - high availability and load balancing. In on-premises deployments, Konvoy ships with Keepalived. Internal defines whether the created load balancer should be available only from within the Virtual Private Cloud where the cluster resides or should it also be reachable from public Internet. Two configuration options are available for each supported cloud provider (below is an example for AWS): kind: ClusterProvisionerĪpiServerPort defines the port on which the cloud provider’s load balancer should listen for incoming requests. The load balancer takes care of health checks and distributing traffic between the control plane nodes. High availability is provided through the cloud provider’s load balancer. Konvoy ships with a highly available control plane, in case of a multi-master Kubernetes deployments.

Controlplane mac alternative