Verifying the TIBCO Mashery Local Cluster on GCP using Kubernetes

To validate Kubernetes cluster deployment, run the following command:
kubectl get nodes
Example output:
NAME                                                                    STATUS    ROLES     AGE       VERSION

gke-ml5-multi-zone-default-pool-2a9026d5-hwv0   Ready     <none>    23h       v1.10.7-gke.2

gke-ml5-multi-zone-default-pool-c02dec31-qb7h   Ready     <none>    23h       v1.10.7-gke.2

gke-ml5-multi-zone-default-pool-e76c960a-q993   Ready     <none>    23h       v1.10.7-gke.2
To validate the TIBCO Mashery Local cluster deployment, run the following command:
kubectl get pods
Example output:
NAME                                              READY   STATUS    RESTARTS   AGE

cache-deploy-0-6fbb7bb985-vzzmq   1/1       Running   0          23h

cache-deploy-1-db874cdf-w9n9k       1/1       Running   0          23h

cache-deploy-2-79465b85d9-t7sd2   1/1       Running   0          23h

cass-set-0-0                                       1/1       Running   0          23h

cass-set-1-0                                       1/1       Running   0          23h

cass-set-2-0                                       1/1       Running   0          23h

cm-deploy-0-664494748d-qsp92      1/1       Running   0          23h

cm-deploy-1-5c54b9dcd8-swbns      1/1       Running   0          23h

cm-deploy-2-698f7c6f88-dz57j         1/1       Running   0          23h

log-set-0-0                                        1/1       Running   0          23h

log-set-1-0                                        1/1       Running   0          23h

log-set-2-0                                        1/1       Running   0          23h

mysql-set-0-0                                   1/1       Running   0          23h

mysql-set-1-0                                   1/1       Running   0          23h

mysql-set-2-0                                   1/1       Running   0          23h

tm-deploy-0-5d6d4c475d-kztk5       1/1       Running   0          23h

tm-deploy-1-c5556574c-5ffv6          1/1       Running   0          23h

tm-deploy-2-545bf95456-4gngh      1/1       Running   0          23h
To test traffic, here are some sample commands:
export LB=`kubectl describe service tm-svc|grep Ingress|awk -F' ' '{print $3}'` && echo $LB
curl -v -H 'Host:api.example.com' http://$LB/v1/api/patient/1234/qatest/testRequestInfo.php?api_key=3bvu8u3p8k5vjxmhrs6tnd6e
Note: All Traffic should go to Load Balancer (going to individual node directly will NOT work.)