The main tools that we can use to troubleshoot issues in Kubernetes are the get and describe commands.
In my experience, the most common problem with running Kubernetes is that, sometimes, certain pods don't start. The steps for troubleshooting are as follows:
- Is the container image correct? A problem with downloading the image will show ErrImagePull. This could be caused if the image can't be downloaded from the registry due to an authentication problem.
- A status of CrashLoopBackOff means that the process for the container has been interrupted. The pod will try to restart over and over. This is normally caused by an underlying issue with the container. Check that the configuration is correct. You can check the stdout logs of a container by using the following command:
$ kubectl logs <pod> -n <namespace> -c <container...
