LATEST VERSION: v1.4 - RELEASE NOTES
Pivotal Container Service v1.3

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 Version Requirements and Hardware Requirements for PKS on vSphere with NSX-T.

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.

Prerequisites

Before installing PKS, you must install Ops Manager. You use Ops Manager to install and configure PKS.

To prepare your vSphere environment for installing Ops Manager and PKS, review the sections below and then follow the instructions in Preparing vSphere Before Deploying PKS.

vSphere Version Requirements

PKS on vSphere supports the following vSphere component versions:

Versions Editions
  • VMware vSphere 6.7 U1 EP06 (ESXi670-201901001) – for NSX-T 2.4
  • VMware vSphere 6.7 U1
  • VMware vSphere 6.7.0
  • VMware vSphere 6.5 U2 P03 (ESXi650-201811002) – for NSX-T 2.4
  • VMware vSphere 6.5 U2
  • VMware vSphere 6.5 U1
  • vSphere Enterprise Plus
  • vSphere with Operations Management Enterprise Plus

Note: VMware vSphere 6.7 is only supported with Ops Manager v2.3.1 or later.

Resource Requirements

Installing Ops Manager and PKS requires the following virtual machines (VMs):

VM CPU RAM Storage
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 Resources

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

Kubernetes Cluster Resources

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

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