Kubernetes: Careful with Clusters

[jeredepp]

It could be dangerous to apply any automated actions without verifying the connected cluster.

For example: Before we deploy we connect to the cluster by issueing, if we would deploy the app on the wrong cluster it could lead to a crash of other systems or it would deploy the app on the wrong cluster.

gcloud container clusters get-credentials production \ master --zone europe-west1-d --project skynet-164509

Following that we should check the clusters nodes by issueing
kubectl get nodes

We could either implement a verification for the connected cluster

Your deploying to the following nodes: 
NAME                                        STATUS    AGE       VERSION
gke-production-default-pool-75420741-031z   Ready     59d       v1.6.4
gke-production-default-pool-75420741-08vv   Ready     48d       v1.6.4
gke-production-default-pool-75420741-fdjm   Ready     48d       v1.6.4
gke-production-default-pool-75420741-j2qn   Ready     60d       v1.6.4
gke-production-default-pool-75420741-l95z   Ready     56d       v1.6.4
gke-production-default-pool-75420741-mlwd   Ready     73d       v1.6.4
gke-production-default-pool-75420741-zk3m   Ready     56d       v1.6.4

Are you sure you want to continue? (y/n)

Or check that we're connected to the right cluster by supplying an env

gke-**environement**-default-pool