HAProxy provides load balancing for developers accessing the Tanzu Kubernetes control plane, and for Kubernetes Services of Type Load Balancer. To support a successful installation of HAProxy, review and satisfy the prerequisites before proceeding with the deployment.
Review the System Requirements for vDS Networking with HAProxy
HAProxy requires vDS networking. Review the system requirements for vDS networking with HAProxy. See System Requirements and Topologies for Setting Up a Supervisor Cluster with vSphere Networking and HAProxy Load Balancing.
It may be helpful to view a demonstration of how to use vSphere with Tanzu with vDS networking and HAProxy. If so, check out the video Getting Started Using vSphere with Tanzu.
Download the HAProxy OVA
VMware provides an HAProxy OVA file that you deploy in your vSphere environment where you will enable Workload Management. Download the latest version of the VMware HAProxy OVA file from the VMware-HAProxy site.
As a convenience, you can import the HAProxy OVA into a Content Library and deploy it from there. See Import the HAProxy OVA to a Local Content Library.
Plan the HAProxy Network Topology
Plan the network topology for deploying the HAProxy load balancer.
There are two network configuration options: Default and Frontend. The default network has 2 NICs: one for the Management network and one for the Workload network. The Frontend network has 3 NICS: Management network, Workload network, and the Frontend network for clients. The table lists and describes characteristics of each network.
The Supervisor Cluster uses the Management network to connect to and program the HAProxy load balancer.
The HAProxy control plane VM uses the Workload network to access the services on the Supervisor Cluster and Tanzu Kubernetes cluster nodes.
External clients (such as users or applications) accessing cluster workloads use the Frontend network to access backend load balanced services using virtual IP addresses.
The diagram below illustrates an HAProxy deployment using a Frontend Network topology. The diagram indicates where configuration fields are expected during the installation and configuration process.