VCF on VxRail provides a way to automate the deployment of a VMware PKS platform within a workload domain. This helps accelerate deployment and access of Kubernetes infrastructure in private, public, and hybrid cloud environments so that application development teams can start deploying container-based applications faster.

The PKS WLD deploys VMware Enterprise PKS which is built on upstream Kubernetes and delivered as an integrated solution. The integration within VCF features automated and centralized life cycle management and operations of the underlying WLD clusters. It includes integrated container networking and network security with NSX-T, is easily scalable, and includes automated deployment and configuration.

PKS workload domain architecture

The PKS WLD architecture is based from VVD-compliant best practices designs. Like the Horizon WLD, a PKS WLD is built on top off pre-provisioned VxRail VI WLD. However, PKS requires the WLD to be NSX-T based due to its tight integration with NSX-T. SDDC Manager fully automates the deployment of PKS components, including PCF Ops Manager, BOSH Director, PKS Control Plane, and optionally, the Harbor Enterprise Container Registry. These management components get deployed on the VxRail NSX-T VI WLD cluster. The NSX-T Edge VMs must be manually deployed and configured before starting the PKS WLD deployment. The following diagram illustrates the component layout for a VCF PKS WLD deployment.

Figure 5.              PKS WLD component layout

Prerequisites for deploying VMware Enterprise PKS

There are several prerequisites that must be met before starting the VCF PKS WLD deployment. An NSX-T VI WLD must first be created within VCF. The NSX-T Edge components must then be manually deployed and configured to allow the PKS components to use the network virtualization features and capabilities that are built into NSX-T, like NorthSouth routing, NAT, and Load Balancing. Following is the list of prerequisites:

• NSX-T VI WLD
• NSX-T Edge VMs are deployed and configured.
• IP/Hostnames for the PKS Management components
• NSX-T segments created for PKS Management and Service networks
• IP block for the Kubernetes Pods
• IP block for the Kubernetes Nodes
• Floating IP pool for the load balancers for each of Kubernetes clusters
• CA-signed certificates for Operations Manager, Enterprise PKS control plane, and Harbor Registry
• Certificate for NSX-T Super User
• Resource Pools created in the VI WLD vCenter that will be mapped as PKS availability zones

For additional details on the prerequisites, see the VCF Admin guide PKS Prerequisites.

Lifecycle Management of the PKS components is accomplished using the native LCM capabilities that are built into the PKS platform. VxRail VI WLD infrastructure LCM is accomplished using SDDC Manager along with the integration that exists with VxRail Manager.