vSphere with NSX-T Prerequisites and Resource Requirements
Page last updated:
This topic describes the prerequisites and resource requirements for installing Pivotal Container Service (PKS) on vSphere with NSX-T integration.
For prerequisites and resource requirements for installing PKS on vSphere without NSX-T integration, see vSphere Prerequisites and Resource Requirements.
PKS supports air-gapped deployments on vSphere with or without NSX-T integration.
You can also configure integration with the Harbor tile, an enterprise-class registry server for container images. For more information, see VMware Harbor Registry in the Pivotal Partner documentation.
PKS on vSphere with NSX‑T supports the following vSphere component versions:
Note: VMware vSphere 6.7 is only supported with Ops Manager v2.3.1 or later and NSX‑T v2.3.
For more information, see Upgrading vSphere in an NSX Environment in the VMware documentation.
Deploying NSX-T requires the additional following component versions:
|VMware NSX-T||2.2, 2.3|
Before you install PKS, you must install one of the following:
- Pivotal Ops Manager v2.2.3 or later
- Pivotal Ops Manager v2.3.1 or later
- Pivotal Ops Manager v2.4.x
Note: You use Ops Manager to install and configure PKS. Each version of Ops Manager supports multiple versions of PKS. To confirm that your Ops Manager version supports the version of PKS that you install, see PKS Release Notes.
To install an Ops Manager version that is compatible with the PKS version you intend to use, follow the instructions in the corresponding version of the Ops Manager documentation.
|Ops Manager v2.2|
|Ops Manager v2.3|
|Ops Manager v2.4|
Installing Ops Manager and PKS requires the following virtual machines (VMs):
|Pivotal Container Service||2||8 GB||16 GB|
|Pivotal Ops Manager||1||8 GB||160 GB|
|BOSH Director||2||8 GB||16 GB|
Each PKS deployment requires ephemeral VMs during installation and upgrades of PKS. After you deploy PKS, BOSH automatically deletes these VMs.
To enable PKS to dynamically create the ephemeral VMs when needed, ensure that the following resources are available in your vSphere infrastructure before deploying PKS:
|Ephemeral VM||Number||CPU Cores||RAM||Ephemeral Disk|
|BOSH Compilation VMs||4||4||4 GB||16 GB|
Each Kubernetes cluster provisioned through PKS deploys the VMs listed below. If you deploy more than one Kubernetes cluster, you must scale your allocated resources appropriately.
|VM||Number||CPU Cores||RAM||Ephemeral Disk||Persistent Disk|
|master||1 or 3||2||4 GB||8 GB||5 GB|
|worker||1 or more||2||4 GB||8 GB||10 GB|
|errand (ephemeral)||1||1||1 GB||8 GB||none|
Deploying NSX-T requires the additional following resources from your vSphere environment:
|NSX-T Component||Instance Count||Memory per Instance||vCPU per Instance||Disk Space per Instance|
|NSX Manager Appliance||1||16 GB||4||140 GB|
|NSX Controllers||3||16 GB||4||120 GB|
|NSX-T Edge||1 up to 8||16 GB||8||120 GB|
For the firewall ports and protocols requirements for using PKS on vSphere with NSX-T integration, see Firewall Ports and Protocols Requirements.
- Complete any confirmation tasks described in the VMware NSX-T Data Center Documentation to verify your configuration before proceeding to the next step.
- Comply with any requirements described in the VMware NSX-T Data Center Documentation.
Note: When you use NSX-T 2.1, creating namespaces with names longer than 40 characters may result in a truncated or hashed name in the NSX-T Manager UI.
Please send any feedback you have to firstname.lastname@example.org.