vSphere with Tanzu supports the NSX Advanced Load Balancer, also known as Avi Load Balancer, Essentials Edition. If you are using vSphere Distributed Switch (vDS) networking for Workload Management, you can install and configure the NSX Advanced Load Balancer in your vSphere with Tanzu environment.
About the NSX Advanced Load Balancer The NSX Advanced Load Balancer provides dynamically scaling load balancing endpoints for Tanzu Kubernetes clusters provisioned by the Tanzu Kubernetes Grid Service.
NSX Advanced Load Balancer Components The components of the NSX Advanced Load Balancer, also known as Avi Load Balancer, include the control plane cluster, data plane VMs, virtual services, and IP address management.
NSX Advanced Load Balancer Requirements To configure vSphere with Tanzu with the NSX Advanced Load Balancer, also known as the Avi Load Balancer, your environment must meet certain requirements. vSphere with Tanzu supports multiple topologies for Avi networking: a single vDS network for the Avi Service Engine and load balancer services, and a vDS for the Avi management plane and another vDS for the NSX Advanced Load Balancer.
Deploy the Controller Deploy the Controller VM to the vSphere Management network in your vSphere with Tanzu environment.
Take a Snapshot of the Controller You can take a snapshot of the Controller VM to preserve the state of the VM so that you can return to that state. You can take a snapshot of the controller VM once it is deployed so that you can revert to its initial state if the configuration does not work as expected.
Power On the Controller Once you deploy the Controller VM, you can power it on. During the boot up process, the IP address specified during the deployment gets assigned to the VM.
Configure the Controller Configure the Controller VM for your vSphere with Tanzu environment.
Assign a License Once you configure the NSX Advanced Load Balancer, you assign an license to it. The Controller boots in the Enterprise edition with an evaluation license. Assign the Essentials license to it.
Assign a Certificate to the Controller The Controller must send a certificate to clients to establish secure communication.
Configure a Service Engine Group You can create Service Engines within a group which defines the placement and number of Service Engine VMs within vCenter. You can also configure high availability.
Configure a Virtual IP Network Configure a virtual IP subnet for the Data network. You can place virtual services on a specific virtual IP network. Configure static IP addresses for the Controller and Service Engines. You can configure DCHP for the Service Engines. If DHCP is unavailable, configure a pool of IP addresses.
Configure Static Routes Configure static routes to create layer 3 connectivity between the virtual IP network and the Workload network, if you require to create Tanzu Kubernetes clusters in dedicated Workload networks.
Configure the IPAM and DNS Profiles Configure the IPAM and DNS Profiles for the Controller and assign them to the Default-Cloud configuration. Currently, only the Default-Cloud configuration is supported.
Test the NSX Advanced Load Balancer After you have deployed and configured the NSX Advanced Load Balancer control plane, verify its functionality.