Debugging Kubernetes issues

In this section, we'll be discussing some of the Kubernetes troubleshooting concerns:

1. The first step to debug the Kubernetes cluster is to list the number of nodes, using the following command:

   $ kubetl get nodes
   

   Also, verify that all nodes are in the ready state.

2. Look at the logs in order to figure out issues in the deployed Kubernetes cluster 

       master:
           var/log/kube-apiserver.log - API Server, responsible for serving the API
           /var/log/kube-scheduler.log - Scheduler, responsible for making scheduling 
       decisions
           /var/log/kube-controller-manager.log - Controller that manages replication 
       controllers
       Worker nodes:
   
           /var/log/kubelet.log - Kubelet, responsible for running containers on the 
       node
           /var/log/kube-proxy.log - Kube Proxy, responsible for service load 
       balancing
   
   

3. If the pod stays in the pending state, use the following command:

   $ cluster/kubectl.sh describe pod podname
   

   This will list events...