I can't read the logs or run exec on the pod, we will help you right now!

SRE/Kubernetes Admin
Flávio Lemes

Hey everyone! Have you ever felt like an astronaut lost in space when you can't access your pod's logs? Well, you are not alone in this drifting ship. Let's solve this mystery worthy of a CSI Miami episode: Kubernetes Edition.
Houston, we have a problem!
Picture this: you are relaxed, drinking your coffee, thinking you're the Tony Stark of Kubernetes, when suddenly... BAM! You can't read the logs or even run a simple exec on the pod. It's as if your cluster turned into Area 51 - nobody goes in, nobody goes out.
Before you panic and start blaming the intern, let's use our Kubernetes Sherlock Holmes skills to investigate. Here is a troubleshooting tip that will make you look like a wizard in front of your colleagues:
1. First, check if the pod is actually running:
If the status isn't "Running", you have other problems.
2. Now, let's try to read the logs manually:
If that doesn't work, don't despair! We have more tricks up our sleeve.
3. Try to run an exec to see what happens:
Solving the mystery
If you've made it this far and nothing worked, we are probably dealing with one of these villains:
Network issue: Your cluster might have some connectivity issues.
Pod in a zombie state: Sometimes, the pod gets stuck in a limbo between life and death.
Kubelet issue: The agent running on each node might be in a bad mood.
Magic solutions
1. Pod debugging:
This creates a debug container in the same pod, allowing a better investigation.
2. Check the pod events:
3. Take a look at the kubelet logs: If you have access to the node, check out:
Conclusion
With these tips, you will solve the mystery of the missing logs and exec's quicker than Scooby-Doo unmasks the villain. Remember: in Kubernetes, issues are like going up a down escalator - they seem impossible at first, but with persistence (and some cool tips), you'll get there!
Until next time, and may your pods always be healthy!
Operating Kubernetes in production for more than 13 years. With Quor, this experience extends to software supply chain security as well.
GET UP
© Getup · 2026
