Stern — Multi-Pod Multi-Container Log Tailing for Kubernetes

What it is

Stern is a CLI tool that tails logs from multiple Kubernetes pods and containers simultaneously. It shows color-coded output with pod and container names, making it easy to follow distributed application logs in real time.

Stern targets SREs, DevOps engineers, and developers debugging Kubernetes workloads. It solves the problem of running multiple kubectl logs -f commands in separate terminals by combining all matching logs into a single stream.

The project is actively maintained and suitable for both individual developers and teams looking to integrate it into their existing toolchain. Documentation and community support are available for onboarding.

How it saves time or tokens

Instead of opening one terminal per pod and mentally correlating timestamps, Stern shows all matching pods in one view with color-coded prefixes. Pod selectors use regex, so you can tail all pods for a deployment with a single pattern. When pods restart or scale, Stern automatically picks up new instances without reconnecting.

How to use

1. Install Stern via Homebrew (brew install stern), Krew, or download the binary from GitHub releases.
2. Run stern <pod-name-pattern> to tail all pods matching the pattern in the current namespace.
3. Use flags to filter by container name, namespace, label selector, or time range.
4. Pipe output to grep or jq for structured log filtering.

Example

# Tail all pods matching 'web-api' in the production namespace
stern web-api --namespace production

# Tail specific container in pods with label selector
stern --selector app=gateway --container nginx

# Show logs from the last 10 minutes in JSON format
stern payment-service --since 10m --output json | jq '.message'

# Tail across all namespaces
stern web --all-namespaces

Related on TokRepo

• AI Tools for DevOps — Other Kubernetes observability and debugging tools.
• AI Tools for Monitoring — Log aggregation and monitoring solutions for production clusters.

Common pitfalls

• Using broad regex patterns in large clusters. A pattern like .* tails every pod and overwhelms your terminal. Be specific with pod name patterns.
• Forgetting the --since flag when debugging. Without it, Stern shows logs from pod start time, which can dump megabytes of old logs.
• Not using --exclude to filter out health check noise. Most services log health check requests every few seconds, cluttering the output.
• Not reading the changelog before upgrading. Breaking changes between versions can cause unexpected failures in production. Pin your version and review release notes.