Verifying the Deployment of a Cluster on AWS using Kubernetes

To validate Kubernetes cluster deployment, run the following command: 
kubectl get nodes
Example output: 
NAME STATUS ROLES AGE VERSION
ip-172-20-49-153.ec2.internal Ready node 3m v1.9.10
ip-172-20-50-219.ec2.internal Ready master 4m v1.9.10
ip-172-20-62-150.ec2.internal Ready node 3m v1.9.10
ip-172-20-63-177.ec2.internal Ready node 3m v1.9.10
To validate Mashery Local cluster deployment, run the following command: 
kubectl get nodes
Example output: 
NAME READY STATUS RESTARTS AGE
cache-deploy-0-544575b5bf-64c2z 1/1 Running 0 1m
cache-deploy-0-544575b5bf-r966c 1/1 Running 0 1m
cache-deploy-0-544575b5bf-sk87l 1/1 Running 0 1m
cass-set-0-0 1/1 Running 0 13m
cass-set-0-1 1/1 Running 0 12m
cass-set-0-2 1/1 Running 0 10m
cm-deploy-0-595dd89974-2ds84 1/1 Running 0 5m
log-set-0-0 1/1 Running 0 5m
log-set-0-1 1/1 Running 0 4m
mysql-set-0-0 1/1 Running 0 2m
tm-deploy-0-7cfbc7cb56-59t2x 1/1 Running 0 1m
tm-deploy-0-7cfbc7cb56-6nwd7 1/1 Running 0 1m
tm-deploy-0-7cfbc7cb56-bnpng 1/1 Running 0 1m
To test traffic, here are some example commands: 
export LB=`kubectl describe service tm-svc|grep Ingress|awk -F' ' '{print $3}'` && echo $LB
 
curl -H 'Host:api.example.com' 'http://<IP from step 1>/hw_path_01?api_key=sra663fmnshjazx5sv2mgtmw'
Note: All Traffic should go to Load Balancer (going to master or slave directly will NOT work.)