Home > Servers > PowerEdge and VMware > White Papers > Kubernetes containers on Dell PowerEdge made easy with VMware Tanzu > Networking considerations
Planning your deployment can help you reduce or avoid networking conflicts. Before beginning the Tanzu deployment, we defined the networking for the cluster. The solution required only one additional network scope (a range of IP addresses).
Our network needed a gateway for successful deployment, and we used a network address translation (NAT) gateway.
The HAProxy deployment refers to the network labels and addresses differently than the VMware Workload Management configuration wizard. Without planning, IT staff may not understand the networking needs for adding Tanzu to a vSphere environment. As you’re planning the networking for your solution, you might need the following addresses:
Note: Once configured, the HAProxy will respond to the HAProxy management and workload addresses as well as the load balancer/virtual server addresses, regardless of whether they’re being used. You provide these addresses again in explicit format during workload management configuration.
Table 2 shows our networking configurations. You can simply replace our network addresses, labels, and VLANs with your own.
Table 2: Networking information for adding VMware Tanzu to our existing VMware vSphere environment on three Dell EMC PowerEdge R740xd servers.