- TechOps Examples
- Posts
- Understanding Kubernetes Logs - A Comprehensive Guide
Understanding Kubernetes Logs - A Comprehensive Guide
Govardhana M K
November 12, 2024
In partnership with
TechOps Examples
Hey — It's Govardhana MK 👋
Along with a use case deep dive, we identify the top news, tools, videos, and articles in the TechOps industry.
Before we begin... a big thank you to today's sponsor GROWTH SCHOOL
AI is advancing faster than ever — and those who don’t adapt risk being left behind. To thrive in this new era, you need more than just basic knowledge — you need mastery.
That’s where our exclusive 2-day AI Mastermind comes in.
A deep dive from 16th -17th November 2024 designed to equip you with the latest AI insights and hands-on skills to set you apart and place you in the Top 1%.
The Mastermind, worth $1495, is FREE for the first 20 participants only! 🎉
Join this Mastermind to:
Gain hands-on experience with cutting-edge AI tools & techniques
Learn practical AI strategies to streamline tasks and make data-driven decisions
Master the art of prompt engineering and unlock the full potential of AI
Collaborate and network with like-minded innovators in an intensive learning environment
Don’t miss out on this chance to upskill with AI in one powerful weekend.
IN TODAY'S EDITION
🧠 Use Case
Understanding Kubernetes Logs - A Comprehensive Guide
🚀 Top News
Kubernetes V1.32 Sneak Peek With Upcoming Changes
📽️ Videos
When to Choose Kubernetes?
Every Protocol Explained As FAST As Possible - SSH, HTTP, SFTP, TCP/IP, DNS, RDP
📚️ Resources
20 Life Hacks For DevOps Engineers
GitOps for CloudFront and S3 walkthrough
🛠️ TOOL OF THE DAY
Terraspace - A Terraform Framework that optimizes for infrastructure-as-code happiness.
Provides an organized structure, conventions over configurations.
Keeps your code DRY, and adds convenient tooling.
🧠 USE CASE
Understanding Kubernetes Logs - A Comprehensive Guide
Not every day you would be setting up clusters; however, there is a huge possibility that every day you would be involved in the operational and troubleshooting aspects of Kubernetes.
Understand the logs plays a crucial role in any K8S practitioner's life.
You can’t miss it or skip it.
I broke down the typical Kubernetes logs directory for easy understanding.
Like other directories, you can park the application logs under '/var/log/', which can further be organized by 'namespace’ and provide insights into the internal statuses of your application.
They are especially valuable for troubleshooting issues and tracking cluster events.
The log directory structure is quite straightforward; rather than spending time going through each one, let’s talk about ‘cluster-level logging’—a less discussed and crucial aspect.
Cluster-level logging architectures
Kubernetes natively doesn’t provide log storage, so cluster-level logging requires independent dedicated backend storage and lifecycle for logs, separate from nodes, pods, and containers.
Here are a few options:
Run a logging agent on each node to collect logs.
Add a sidecar container in the application pod specifically for logging.
Send logs directly from the application to a logging backend.
1. Node logging Agent
Ref: Kubernetes Documentation
To implement cluster-level logging, deploy a node-level logging agent on each node, typically as a DaemonSet, to collect and forward logs to a backend.
This agent, running as a container, accesses log directories from all application containers on the node.
Node-level logging creates one agent per node without needing changes to applications.
Containers log to stdout and stderr in varied formats, which the node-level agent gathers for aggregation.
2. Streaming Sidecar Container
Ref: Kubernetes Documentation
By configuring sidecar containers to write to their own stdout and stderr streams, you can leverage the kubelet and node-level logging agent already running on each node.
Sidecars read logs from sources like files, sockets, or journald and output to separate streams, enabling multiple log streams for different application parts.
This setup supports components that don’t natively log to stdout or stderr, with minimal redirection overhead.
Since kubelet manages stdout and stderr, you can easily access logs using tools like kubectl logs.
3. Sidecar Container With a Logging Agent
Ref: Kubernetes Documentation
If the node-level logging agent doesn’t meet your needs, you can add a sidecar container with a logging agent set up specifically for your application.
4. Pushing Logs Directly From The Application
Ref: Kubernetes Documentation
Logging that involves directly exposing or pushing logs from each application is outside the scope of Kubernetes, though it can be an option for specific cases, like when an application requires direct integration with an external logging service.
Hope this was useful in clarifying a few questions related to Kubernetes logs.
Learn AI in 5 minutes a day
This is the easiest way for a busy person wanting to learn AI in as little time as possible:
Sign up for The Rundown AI newsletter
They send you 5-minute email updates on the latest AI news and how to use it
You learn how to become 2x more productive by leveraging AI