From the course: Certified Kubernetes Administrator (CKA) Cert Prep

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Understanding the troubleshooting flow

Understanding the troubleshooting flow - Kubernetes Tutorial

From the course: Certified Kubernetes Administrator (CKA) Cert Prep

Start my 1-month free trial Buy for my team

Understanding the troubleshooting flow

“

- [Instructor] Okay, let's try to understand the troubleshooting flow. Resources are first created in the Kubernetes etcd database. And kubectl describe and kubectl events, will show you at that level what has been going on. So if kubectl describe is showing something like pending, well, that means that there is a problem in a very early stage. After adding the resources to the database, the Pod application is started on the nodes where it is scheduled. Oh, and let's not forget that first, before it can be started, the Pod image need to be fetched. A useful command is sudo crictl images, which will give you a list of the images that have been fetched. And once the application is started, if anything goes wrong, you can use kubectl logs to read the output of the application. And if the application has been started and still is problematic, you can use an interactive shell using kubectl exec -it on your port, followed by -- sh. That'll start a shell and allow you to investigate what is…

Contents