- Pivotal Container Service (PKS) Version 1.0
- Pivotal Cloud Foundry BOSH
- VMware NSX-T
- Supported by vSphere and Google Cloud Platform (GCP)
PKS uses the On-Demand Broker to deploy Cloud Foundry Container Runtime, a BOSH release that offers a uniform way to instantiate, deploy, and manage highly available Kubernetes clusters on a cloud platform using BOSH. Check the PKS Components list in PKS Docs. Download PKS. You need either Google Cloud Platform (GCP) or vSphere as your infrastructure with Operations Manager 2.0. If you are installing PKS to vSphere, you can also configure integration with NSX-T (integrated with PKS download from Pivotal Network) and Harbor (tile to come live on Pivnet). If you have bought the NSX-T license, you should have a license pack from the Platform or Sales team already. The NSX-T for PAS tile is available for download on Pivotal Network https://network.pivotal.io/products/vmware-nsx-t.
Pivotal Docs has a detailed description of
- Installing PKS with NSX-T Integration
- Installing PKS on vSphere
- Installing PKS on GCP
- Integrating VMware Harbor Registry with PKS
- Managing PKS that covers the instructions to configure PKS API Access, Manage Users in UAA, Manage PKS Deployment with Bosh, Customization of Workloads, and how to delete PKS.
- In PKS 1.0, UAA has been added. It means that before you can create a cluster you need to create a UAA user per the following steps in the documentation https://docs.pivotal.io/runtimes/pks/1-0/manage-users.html
- Once you create your UAA user and password you can then use them to log on to the PKS API 'pks login -a PKS_API -u USERNAME -p PASSWORD'; see docs https://docs.pivotal.io/runtimes/pks/1-0/create-cluster.html.
- Refer to the Using PKS docs to understand how to Create a Cluster, planning, listing, configuration, and details of clusters, instructions of deploying and accessing the workloads, how to delete a cluster, and how to log out of the PKS Environment.
Known Issues and Workarounds:
- Cannot Access Add-On Features or Functions provided by a Kubernetes add-on
- Workaround for Error:
post-start scripts failedand
Failed JobsAfter deploying PKS, Ops Manager runs scripts to start a number of jobs. You must configure Ops Manager to automatically run these post-deploy scripts.
- Error:`lookup vm-WORKER-NODE-GUID on IP-ADDRESS: no such host` find details here
Read more about PKS and request info from https://pivotal.io/platform/pivotal-container-service