vSphere Prerequisites and Resource Requirements
Page last updated:
Warning: Pivotal Container Service (PKS)
v1.4 is no longer supported because it has reached the End
of General Support (EOGS) phase as defined by the
Support Lifecycle Policy.
To stay up to date with the latest software and security updates, upgrade to a supported version.
This topic describes the prerequisites and resource requirements for installing Enterprise Pivotal Container Service (Enterprise PKS) on vSphere.
For prerequisites and resource requirements for installing Enterprise PKS on vSphere with NSX-T integration, see vSphere with NSX-T Version Requirements and Hardware Requirements for Enterprise PKS on vSphere with NSX-T.
Enterprise 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.
Before you install Enterprise PKS, you must do the following:
- Review the sections below
- Complete the procedures in Preparing vSphere Before Deploying Enterprise PKS
For vSphere version requirements for Enterprise PKS, refer to the VMware Product Interoperability Matrices.
Installing Ops Manager and Enterprise 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|
Storage Requirements for Large Numbers of Pods
If you expect the cluster workload to run a large number of pods continuously, then increase the size of persistent disk storage allocated to the the Pivotal Container Service VM as follows:
|Number of Pods||Storage (Persistent Disk) Requirement ^*|
|1,000 pods||20 GB|
|5,000 pods||100 GB|
|10,000 pods||200 GB|
|50,000 pods||1,000 GB|
Ephemeral VM ResourcesEach Enterprise PKS deployment requires ephemeral VMs during installation and upgrades of Enterprise PKS. After you deploy Enterprise PKS, BOSH automatically deletes these VMs. To enable Enterprise PKS to dynamically create the ephemeral VMs when needed, ensure that the following resources are available in your vSphere infrastructure before deploying Enterprise PKS:
|Ephemeral VM||Number||CPU Cores||RAM||Ephemeral Disk|
|BOSH Compilation VMs||4||4||4 GB||32 GB|
Kubernetes Cluster Resources
Each Kubernetes cluster provisioned through Enterprise 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||50 GB|
|errand (ephemeral)||1||1||1 GB||8 GB||none|
For a complete list of network communication requirements for vSphere without NSX-T, see Firewall Ports and Protocols Requirements for vSphere without NSX-T.
Please send any feedback you have to firstname.lastname@example.org.