Pivotal Container Service Introductory Walkthrough


Before You Begin

Before you begin this walkthrough ensure you are logged onto the PKS desktop by following the instructions found here.


Section 1: Log in to the PKS CLI

On your Pivotal Container Service Desktop, launch PowerShell

Run the following command to get the PKS version and a list of available PKS CLI options

$ pks -h



Login to the PKS environment using your PKS credentials from the Pivotal Container Service tile on the TestDrive Portal

$ pks login -a pks-api.vmwdemo.int -u <username> -p <password> -k



Section 2: Creating a Kubernetes Cluster

On your Pivotal Container Service Desktop, launch PowerShell

Deploy a Kubernetes Cluster using the command below, following the cluster naming convention of <username>-<num>. Cluster creation can take somewhere between 10-15 minutes based on the active load on the system infrastructure

$ pks create-cluster <username>-1 -e <username>-1.vmwdemo.int --plan small

The domain name "*.vmwdemo.int" should remain the same as this is the domain name for this environment. Please follow the following naming convention 


NOTE: Please do NOT create more than 2 k8s clusters


When cluster creation is initiated, BOSH creates k8s Master and Worker instances on an ESX datastore. To check this out, launch the vSphere Client shortcut on your desktop and login using the credentials given below, and observe the VMs getting created under the Compute Cluster.

URL: https://pks-vc-1.vmwdemo.int/vsphere-client
Username: pksdemo@vsphere.local
Password: PKSdemo123!



Next, let’s observe the automated network creation in NSX. Launch the NSX Manager shortcut from desktop and login using the credentials below. To provide a strong isolation boundary, PKS spawns new routers, logical switches and load balancers for each namespace in the k8s cluster. Each of these network infrastructure entries includes the cluster UUID in their name, making it easy for users to identify the ones created for their cluster

URL: https://pks-nsxtmgr-1.vmwdemo.int 
Username: audit
Password: PKSdemo123!

T1 router with router name same as the UUID of the created clusterPicture8.png

Logical switches with the same UUIDPicture9.png

Load Balancer created automatically for our clusterPicture10.png


At this point, we will go back to the PKS CLI and check if cluster has been deployed.

Run the following command to list down all the k8s clusters created by your user

$ pks clusters


Get details of the cluster you created by using the command below

$ pks cluster <username>-1



Section 3: Preparing to deploy your application

Get k8s Cluster Credentials

This command will populate the kube config file with the right credentials for the cluster

$  pks get-credentials <username>-1


List all the namespaces

$  kubectl get namespaces


List the PODs in all namespaces

$  kubectl get pods --all-namespaces


Section 4: Deploy Restaurant Review Application

Now you can deploy your application. This is done using the kubectl apply command and pointing to the appropriate yaml configuration files. You may have to run get pods a couple of times until the STATUS changes to running 

$ C:\PKS\apps

$ cat rest-review.yaml



Note that we can combine all of our deployments and services into a single file, and also notice that the image is harbor.vmwdemo.int/library/restreview-ui:V1 which is the private Container Registry called Harbor. 

[SC] Harbor showing the rest-review application


[SC] Harbor with vulnerability scanning



Run the application

$ kubectl apply -f rest-review.yaml 

Check the status of PODs

$ kubectl get pods

List deployments

$ kubectl get deployments

Get number of Replica Sets

$  kubectl get rs


Get External LoadBalancer IP

Get external IP to reach your application by running the command below and fetching the External IP against yelb-ui

$  kubectl get svc



View The Application:

  1. Open  Google Chrome
  2. Enter the EXTERNAL-IP from the kubectl get svc. It should be in the format 192.168.x.x


Enter Votes in the Application

The restaurant review application lets you vote as many times as you want for each restaurant. Try opening multiple browsers and voting from each of them. You will see that the application is caching the page views and persisting the vote totals to the Postgres database.

Play around with Votes and page views


Show LB rules in NSX

[SC] Load balancer for this IP



Delete application

Run the following commands to delete the application

$ kubectl delete -f rest-review.yaml


PCF Ops Manager





For Additional Support

Review Our Knowledge Base

Have more questions? Submit a request

Please sign in to leave a comment.