From the course: Debugging Kubernetes
Unlock this course with a free trial
Join today to access over 25,300 courses taught by industry experts.
Solving slow Pods - Kubernetes Tutorial
From the course: Debugging Kubernetes
Solving slow Pods
- [Instructor] Here's another common problem that you might encounter. You have a pod that's running and ready. However the app itself is running really, really, really slowly. The app in the pod is definitely running more slowly than it does via Docker on your machine or how it ran in its previous medium like a VM. What gives, how do we fix something like this? There are several reasons why you might find yourself in this situation. The foremost common ones are either bugs in applications that only manifest when it's run within a container orchestrator, aggressive resource limits defined within the pod like the pod requesting much less memory than the application really needs during peak operations, frequent restarts, or not enough copies or replicas of that pod are running to satisfy the number of requests that it's getting. We already saw what we could do to address pods that restart frequently or have aggressive resource limits in earlier videos. so let's spend some time learning…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
-
(Locked)
Troubleshooting Pods that won't fit in the cluster7m 15s
-
(Locked)
Debugging missing Pod tolerations and taints6m 52s
-
(Locked)
Conquering Pods with pending dependencies9m 36s
-
(Locked)
Debugging ImagePullBackOff errors for non-existent images5m 12s
-
(Locked)
Solving network-related ImagePullBackOff errors1m 33s
-
(Locked)
Solving ImagePullBackOff errors related to private registries12m 2s
-
(Locked)
Debugging CrashLoopBackOff errors and crashing Pods8m 39s
-
(Locked)
Debugging failing liveness probes6m 25s
-
(Locked)
Solving failing Pod readiness checks4m 43s
-
(Locked)
Solving slow Pods13m 2s
-
(Locked)
Challenge: A troublemaking deployment1m
-
(Locked)
Solution: A troublemaking deployment7m 7s
-
(Locked)
-
-
-