The Deployment of a vSphere with Tanzu Workload Domain in the First Region documentation provides step-by-step instructions for installing and configuring a workload domain that can run vSphere with Tanzu, formerly known as vSphere with Kubernetes, workloads, based on VMware Validated Design.
The Deployment of a vSphere with Tanzu Workload Domain in the First Region documentation does not contain step-by-step instructions for performing all required post-configuration tasks because their nature often depends on the requirements of your organization.
The Deployment of a vSphere with Tanzu Workload Domain in the First Region documentation is intended for cloud architects, infrastructure administrators, and cloud administrators who are familiar with and want to use VMware software to deploy in a short time and manage a software-defined data center (SDDC) that meets the requirements for capacity, scalability, backup and restore, and extensibility for disaster recovery support.
Supported VMware Cloud Foundation Version
Deployment of a Virtual Infrastructure Workload Domain in the First Region is compatible with VMware Cloud Foundation 4.1.
Required VMware Software
The Deployment of a vSphere with Tanzu Workload Domain in the First Region documentation is compliant and validated with certain product versions. For more information about supported product versions, see VMware Validated Design Release Notes.
Before You Apply This Guidance
The sequence of the documentation of this design follows the stages for implementing and maintaining an SDDC.
|Workload Domain||Management Component||Deployment Method|
|Management domain||ESXi hosts||Manual deployment|
|vCenter Server||Automated deployment by using Cloud Builder|
|NSX-T Manager and NSX-T Edge nodes with a region-specific and cross-region virtual network segments||Automated deployment by using Cloud Builder|
|vSAN as principal storage||Automated deployment by using Cloud Builder|
|NFS as supplemental storage||Manual deployment|
|SDDC Manager||Automated deployment by using Cloud Builder|
|Region-specific Workspace ONE Access instance connected to NSX-T||Manual deployment|
To apply Deployment of a vSphere with Tanzu Workload Domain in the First Region, you must:
Complete the Planning and Preparation Workbook with your deployment options included.
Deploy a single-region SDDC management domain. See Deployment of the Management Domain in the First Region.
Optionally, read Architecture and Design for a vSphere with Tanzu Workload Domain.
Optionally, read vSphere with Tanzu Configuration and Management. See the vSphere with Tanzu product documentation on the vSphere documentation page.
The same requirement applies if you are following the VMware Cloud Foundation documentation to deploy a virtual infrastructure workload domain. See the VMware Cloud Foundation documentation.
Using VMware Cloud Foundation for Deployment of the Workload Domain in the First Region
VMware Validated Design uses SDDC Manager in VMware Cloud Foundation for automated deployment and life cycle of the components for the workload domains.
VMware Validated Design follows an example naming convention. The naming provides uniqueness of the objects across the SDDC. You can identify managed objects directly if you use many components that are linked together, for example, multiple vCenter Server systems working in Enhanced Linking Mode. For information on the naming convention, see Planning and Preparation Workbook.
|Operation Type||By Using SDDC Manager Automation||Manual Configuration|
|Preparation for deployment||-||Install and configure ESXi on the physical servers.|
|Deployment of the workload domain||
||Create a network pool and commission ESXi hosts for the workload domain.|
|Post-deployment configuration of the workload domain||Replace certificates for the SDDC components of the workload domain.||
|Deployment of vSphere with Tanzu||Deploy vSphere with Tanzu.||
This Deployment of a vSphere with Tanzu Workload Domain in the First Region is updated with each release of the product or when necessary.
|20 OCT 2020||Added a procedure to reconfigure the vSphere Distributed Switch. See Change the Allocation of Host Network Adapters to the Distributed Uplink Port Groups for the Virtual Infrastructure Workload Domain in Region A.|
|14 OCT 2020||Changed the names of the custom attributes that you create in the deployment section to align with the vSphere with Tanzu product name.|
|09 OCT 2020||BGP Autonomous System Number (ASN) allocation numbers updated to match the Planning and Preparation Workbook.|
|06 OCT 2020||Initial release.|