The NSX-T load balancer creates a load balancer service for each Kubernetes cluster provisioned by Enterprise PKS with NSX-T. For each load balancer service, NCP, by way of the CRD, creates corresponding NSXLoadBalancerMonitor objects.
By default Enterprise PKS deploys the following NSX-T virtual servers for each Kubernetes cluster:
One TCP layer 4 load balancer virtual server for the Kubernetes API server.
One TCP layer 4 auto-scaled load balancer virtual server for each Kubernetes service resource of
type:LoadBalancerTwo HTTP/HTTPS layer 7 ingress routing virtual servers. These virtual server are attached to the Kubernetes Ingress Controller cluster load balancer service and can be manually scaled. Enterprise PKS uses Kubernetes custom resources to monitor the state of the NSX-T load balancer service and scale the virtual servers created for ingress.
For information about configuring the layer 7 ingress controller see https://docs.pivotal.io/pks/1-7/network-profiles-ncp-ingress.html
For information about configuring layer 7 ingress routing load balancers see https://docs.pivotal.io/pks/1-7/nsxt-ingress-scale.html
For more information about the NSX-T Load Balancer, see https://docs.vmware.com/en/VMware-NSX-T-Data-Center/2.4/administration/GUID-91F2D574-F469-481A-AA39-CD6DBC9682CA.html
