The network topology for a Supervisor Cluster deployed using the vSphere networking stack, and a HAProxy load balancer is being planned.
In addition to the control plane management IP range and services IP range, how many non-overlapping IP address ranges are needed?
In planning the network topology for a Supervisor Cluster using vSphere networking stack and HAProxy load balancer, it is essential to have separate, non-overlapping IP address ranges for different types of traffic. Besides the control plane management IP range and services IP range, you need two additional IP address ranges: one for the workload network and another for the Kubernetes services CIDR range. This brings the total to four ranges, but since the question asks for additional ranges beyond the already given control plane and services IP ranges, you only need two more non-overlapping IP address ranges.
I would say answer D (2 more), so in addition to the control plane management IP range and services IP range I would add Workload network range and Kubernetes range 1. An IP range for the nodes of the Supervisor Cluster and Tanzu Kubernetes cluster (mgmt) 2. A dedicated IP range for virtual IPs. The HAProxy VM must be the only owner of this virtual IP range. The range must not overlap with any IP range assigned to any Workload Network owned by any Supervisor Cluster. (services) 3. The workload network must be on a different subnet than the management network. 4. Kubernetes services CIDR range. A private CIDR range to assign IP addresses to Kubernetes services. You must specify a unique Kubernetes services CIDR range for each Supervisor Cluster. https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-C3048E95-6E9D-4AC3-BE96-44446D288A7D.html#GUID-C3048E95-6E9D-4AC3-BE96-44446D288A7D
i say 02 range one for Tanzu LB VIp and at least one for a Workload Network
Correct answer is B. as you typically need one additional non-overlapping IP address range for the services IP range.