LATEST VERSION: v1.1 - RELEASE NOTES
Pivotal Container Service v1.0

vSphere Prerequisites and Resource Requirements

Page last updated:

This topic describes the prerequisites and resource requirements for installing Pivotal Container Service (PKS) on vSphere with or without NSX-T integration.

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.

Component Version Requirements

vSphere Version Requirements

PKS on vSphere supports the following vSphere component versions:

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

NSX-T Integration Version Requirements

Deploying NSX-T requires the additional following component versions:

Component Version
VMware NSX-T 2.1

Resource Requirements

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

VM CPU RAM Storage
Pivotal Container Service 1 4 GB 20 GB
Pivotal Ops Manager 1 8 GB 160 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 Name Number CPU Cores RAM Ephemeral Disk Persistent Disk
master 1 2 4 GB 8 GB 5 GB
worker 1 2 4 GB 8 GB 10 GB

NSX-T Integration Resource Requirements

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

Installing PKS on vSphere with NSX-T

For information about the firewall ports and protocols requirements for using PKS on vSphere with NSX-T, see Firewall Ports and Protocols Requirements for vSphere with NSX-T.

To install and configure PKS with NSX-T integration, follow the procedures below:

  1. Installing and Configuring PKS with NSX-T Integration
  2. (Optional) Installing and Integrating VMware Harbor Registry with PKS

Installing PKS on vSphere without NSX-T

To install PKS on vSphere without NSX-T integration, follow the procedures below:

  1. Preparing to Deploy PKS to vSphere
  2. Deploying Ops Manager to vSphere
  3. Configuring Ops Manager on vSphere
  4. Installing and Configuring PKS
  5. (Optional) Installing and Integrating VMware Harbor Registry with PKS

About Deploying PAS and PKS

The Pivotal Application Service (PAS) and PKS runtime platforms are both deployed by Ops Manager using BOSH. You can deploy both PAS and PKS using the same Ops Manager instance in a development or test environment, but we recommend that you deploy production installations of PAS and PKS to separate Ops Manager instances. For increased security, we recommend deploying each Ops Manager instance using a unique cloud provider account.

Separate installations of Ops Manager 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