How to do it…

Follow these steps to gather cluster information in order to troubleshoot potential issues: 

1. Create a file dump of the cluster state called cluster-state:

$ kubectl cluster-info dump --all-namespaces \
 --output-directory=$PWD/cluster-state

2. Display the master and service addresses:

$ kubectl cluster-info
Kubernetes master is running at https://172.23.1.110:6443
Heapster is running at https://172.23.1.110:6443/api/v1/namespaces/kube-system/services/heapster/proxy
KubeDNS is running at https://172.23.1.110:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

3. Show the resource usage of the us-west-2.compute.internal node:

$ kubectl top node us-west-2.compute.internal
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
us-west-2.compute.internal 42m 2% 1690Mi 43%

4. Mark the us-west-2.compute.internal node as unschedulable:

$ kubectl cordon us-west-2.compute.internal

5. Safely evict all the pods from the us-west-2.compute.internal node for maintenance:

$ kubectl drain us-west-2.compute.internal

6. Mark the us-west-2.compute.internal node as schedulable after maintenance:

$ kubectl uncordon us-west-2.compute.internal