Using Enterprise PKS
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 section describes how to use Enterprise Pivotal Container Service (Enterprise PKS).
Note: Because Enterprise PKS does not currently support the Kubernetes Service Catalog or the GCP Service Broker, binding clusters to Kubernetes services is not supported.
The procedures for using Enterprise PKS have the following prerequisites:
You must have an external TCP or HTTPS load balancer configured to forward traffic to the PKS API endpoint. For more information, see the Configure External Load Balancer section of Installing Enterprise PKS for your IaaS.
You must know the address of your PKS API endpoint and have a UAA-created user account that has been granted Enterprise PKS cluster access. For more information, see Managing Users in Enterprise PKS with UAA.
Note: If your Enterprise PKS installation is integrated with NSX-T, use the DNAT IP address assigned in the Retrieve the Enterprise PKS Endpoint section of Installing Enterprise PKS on vSphere with NSX-T Integration.
See the following topics:
- Logging in to Enterprise PKS
- Accessing Dashboard
- Deploying and Exposing Basic Workloads
- Getting Started with VMware Harbor Registry
- Using Helm with Enterprise PKS
- Configuring and Using Dynamic PersistentVolumes
- Creating Sink Resources
- Logging Out of Enterprise PKS
- Viewing Usage Quotas
Please send any feedback you have to email@example.com.