Home > Storage > PowerStore > Virtualization and Cloud > Dell PowerStore: VMware vSphere with Tanzu and TKG Clusters > Deploying vSphere with Tanzu
After PowerStore storage and vSphere infrastructure is prepared and configured, vSphere with Tanzu can be deployed. Deployment is accomplished by enabling Workload Management in the vSphere UI. VMware details this process in the document vSphere with Tanzu Configuration and Management. The following steps are shown as an example using NSX-T for networking and PowerStore for the storage:
Note: VMware recommends using Storage DRS with anti-affinity rules to maintain Control Plane Node VMs on separate datastores. The datastore Tag and VM Storage Policy must apply to all the datastores in the datastore cluster, and the datastore cluster itself. Deploy the Control Plane Nodes to the VM Storage Policy associated with the datastore cluster. After deployment, create and apply the Storage DRS anti-affinity rules which will move the Control Plane Nodes so that each is on a unique datastore.
vSphere Pods enable SCSI bus sharing and if they are deployed on a Datastore Cluster, the individual datastores in the Datastore Cluster cannot be placed in maintenance mode. A Datastore Cluster loses some of its functionality if used for placement of vSphere with Tanzu Ephemeral Disks.
Once the deployment is complete, use the vSphere UI to go to Hosts and Clusters. Left click on the cluster object. From Monitor | Namespaces | Overview page provides information about the Supervisor Cluster, Kubernetes version and status, and the Control Plane Nodes. The Control Plane Node IP Address should be HTTPS accessible in a web browser from the workload/DevOps network. This is where the Kubernetes CLI Tools can be downloaded and installed from. After the Kubernetes CLI Tools are installed, the Control Plane Node IP Address serves as the API endpoint that kubectl commands will be issued against.