LATEST VERSION: v1.2 - RELEASE NOTES
Pivotal Container Service v1.2

vSphere Prerequisites and Resource Requirements

Page last updated:

This topic describes the prerequisites and resource requirements for installing Pivotal Container Service (PKS) on vSphere.

For prerequisites and resource requirements for installing PKS on vSphere with NSX-T integration, see vSphere with NSX-T 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 the VMware Harbor Registry documentation.

vSphere Version Requirements

PKS on vSphere supports the following vSphere component versions:

Versions Editions
  • VMware vSphere 6.7*
  • VMware vSphere 6.5 U2
  • VMware vSphere 6.5 U1
  • VMware vSphere 6.5 GA
  • vSphere Enterprise Plus
  • vSphere with Operations Management Enterprise Plus

* VMware vSphere 6.7 is only supported on Ops Manager v2.3 and NSX-T v2.3.

Resource Requirements

Installing PKS deploys the following two virtual machines (VMs):

VM CPU RAM Storage
Pivotal Container Service 2 8 GB 16 GB
Pivotal Ops Manager 1 8 GB 160 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 32 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 50 GB
errand (ephemeral) 1 1 1 GB 8 GB none

About Deploying PAS and PKS

The Pivotal Application Service (PAS) and PKS runtime platforms are both deployed by Ops Manager using BOSH. We do not recommend deploying both PAS and PKS using the same Ops Manager instance for security reasons. For even stronger security, we recommend deploying each Ops Manager instance using a unique cloud provider account.

Separate installations of Ops Manager also allow you to customize and troubleshoot runtime tiles independently. You may choose to configure Ops Manager with different settings for your PAS and PKS deployments. For example, PKS and many PAS features depend on BOSH DNS.

If you deploy PAS to a separate Ops Manager instance, you can disable BOSH DNS for troubleshooting purposes. PAS can run without BOSH DNS, but key features such as secure service credentials with CredHub, service discovery for container-to-container networking, and NSX-T integration do not work when BOSH DNS is disabled.

If you deploy PAS and PKS to the same Ops Manager instance, you cannot disable BOSH DNS without breaking your PKS installation along with the PAS features that depend on BOSH DNS.


Please send any feedback you have to pks-feedback@pivotal.io.

Create a pull request or raise an issue on the source for this page in GitHub