TechOps Examples
Hey — It's Govardhana MK 👋
Welcome to another technical edition.
Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.
Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities and articles.
Top engineers at Anthropic and OpenAI say AI now writes 100% of their code.
If you're not using AI, you're spending 40 hours doing what they do in 4.
These 100+ Claude Code hacks fix that and help you ship 10x faster.
Sign up for The Code and get:
100+ Claude Code hacks used by top engineers — free
The Code newsletter — learn the latest AI tools, tips, and skills to code faster with AI in 5 minutes a day
🛠️ TOOL OF THE DAY
eks_demo - Deploys complete EKS cluster including Persistent Storage, Load Balancer, and demo app.
🧠 USE CASE
Kubernetes Logs BreakDown
In Kubernetes troubleshooting logs are gold.
But here is the catch. Not all logs are equal. Not all log locations are obvious.
Whether you are debugging a crashing pod a scheduling delay or a sudden cluster issue you need to know exactly where to look. This can save hours and protect your production.
Most engineers stop at container logs or use only kubectl logs.
Experienced engineers go deeper. They check node logs kubelet logs control plane logs container runtime logs and CNI plugin logs.
To make this easier I have broken down Kubernetes logging into two practical views.
First I have shared a table that outlines the main Kubernetes log types their file paths and what each one means.
Use it as a quick reference when you are troubleshooting.
Download a high resolution copy of this diagram here for future reference.
Next I have included a visual layout of how these logs are structured under the var log directory.
This helps you follow the issue from the container level to the control plane.
Download a high resolution copy of this diagram here for future reference.
My experience says:
➤ Always check both container logs and pod logs when diagnosing container issues
➤ Review error log files under kubelet the API server and the scheduler to uncover hidden problems
➤ For pods stuck in the ContainerCreating state inspect CNI logs such as flannel log or calico log
➤ Use syslog messages dmesg log and auth log to examine node level or system problems
➤ For access and permission issues check the audit logs of the API server especially with RBAC
When you know where the logs are you stop guessing and start fixing
Looking to promote your company, product, service, or event to 49,000+ Cloud Native Professionals? Let's work together.
