Pre-provisioned Built-in Virtual IP

As explained in Define the Control Plane Endpoint, we recommend using an external load balancer for the control plane endpoint, but provide a built-in virtual IP when an external load balancer is not available. If an external load balancer is not available, use the built-in virtual IP.

The virtual IP is not a load balancer; it does not distribute request load among the control plane machines. However, if the machine receiving requests does not respond to them, the virtual IP automatically moves to another machine. The built-in virtual IP uses the kube-vip project. To use the virtual IP, add these flags to the create cluster command:

Virtual IP Example

dkp create cluster preprovisioned \
    --cluster-name ${CLUSTER_NAME} \
    --control-plane-endpoint-host 196.168.1.10 \
    --virtual-ip-interface eth1
    --pre-provisioned-inventory-file preprovisioned_inventory.yaml 
    --ssh-private-key-file <path-to-ssh-private-key> 
    --self-managed

Next Step

Pre-provisioned Use HTTP Proxy

If none of the customizations apply, continue to installation instructions for your environment:

• Pre-provisioned Install in a Non-air-gapped Environment
  OR

• Pre-provisioned Install in an Air-gapped Environment