Home > Servers > PowerEdge and VMware > White Papers > Kubernetes containers on Dell PowerEdge made easy with VMware Tanzu > Completing prerequisites: Tasks 1 through 4
We created our DvS with one port group dedicated for the workload network. This was the network that the Tanzu components used for communication within the K8s cluster. Our process took 19 steps, but if you already have a DvS, you can simply add the Port Group with any required virtual local area network (VLAN) tags, which could take as few as 4 steps. Also of note: The Tanzu environment required a management network to communicate with the vSphere environment, DNS, and other internet-based resources, and we used the default VM network.
For our deployment, we created a dedicated DevOps user in vSphere to access the K8s resources and assigned permissions. Environments and permissions will vary based on many factors. This process required 6 simple steps.
We created the necessary content libraries (centralized repositories to help manage and distribute VMs, scripts, and other files for VMs) that vSphere used to deploy the HAProxy appliance and the Tanzu K8s images. It took us 12 steps to create and populate the HAProxy library. The Tanzu Kubernetes Grid (TKG) library, a subscribed content library, required 7 more steps.
We created a storage tag, which allows you to create tag-based policies, and assigned it to the target storage. Our shared storage was a network file system (NFS) share accessible by all ESXi hosts in the cluster. This straightforward process required only 8 steps.
We also created a VM Storage policy utilizing the storage tag, which defined the target storage for Tanzu VM placement, in 10 steps.