Now for the moment of truth, it is time to deploy Tanzu. Assuming all the prerequisites are configured correct, this is actually a pretty straightforward process.

Start by going to Workload Management, this is under the main vCenter navigation pane.

On the Workload Management page, lets click Get Started.

Select our vCenter and our VDS as we have not done NSX in this deployment.

Choose a name for the Supervisors, select the cluster where Tanzu will be deployed and optionally choose a vSphere Zone name.

Choose the Storage Policy we created previously.

On the Load Balancer page, fill out the networking information you determined earlier, and enter the certificate for HAProxy. Click Next.

There are a couple of ways to obtain the certificate from above.

  • Utilize the script on Tanzu QuickStart. Basically the certificate info gets set as a VM Advanced Property which the powercli script can pull
  • SSH into HAProxy and grab the contents of /etc/haproxy/ca.crt.

Next, we need to enter the Management network information. I am utilizing DHCP for mine.

The network info for the Workload network we discussed in an earlier post, but as a quick reminder

Workload IP Range: – 200
Workload Network Gateway IP:

The Internal Network for Kubernetes Services you should not need to adjust. I would also only adjust that value if you know what you are doing as it can really mess up the deployment.

Select the content library we created.

And select the size of the deployment. For my smaller homelab, I chose the smallest which is “Tiny”

Once you hit finish you will be taken back to the Workload Management -Supervisors page and you should see everything start configuring.

A couple of things to note here. My deployment takes a really long time. I think that is at least partially due to my storage being a bit slower. Don’t be surprised though if it does take a while.

Also if it does encounter some kind of error, depending on the error, Tanzu may be able to resolve the issue. This is because Tanzu works on a declarative state model. In this instance, it means Tanzu will try again if something doesn’t work the first time. Obviously, if you entered IP or DNS information incorrectly though, Tanzu can’t fix that for you. You are able to go into some of the configuration settings you created though and adjust some values if you did fudge an IP address or something.

For instance, if I give Tanzu the wrong values for the HAProxy account, I may eventually see an error like this:

I am able to fix this by going into the configuration and adjusting the provided information to Tanzu.

The change will not necessary take place immediately, but the next attempt Tanzu makes will use the new values.

Assuming everything goes well, and there are no issues you should be able to see this beautiful green config status.

Congratulations! You have Deployed Tanzu! Unfortunately we still have a few steps before we can deploy anything to Tanzu.