Skill Detail
Tail multi-pod Kubernetes logs by label during incidents with Stern
Aggregate and follow logs from matching Kubernetes pods during incident triage without hopping pod by pod.
Runbooks & DiagnosticsMulti-Framework
Runbooks & Diagnostics
Multi-Framework
Security Reviewed
β 4.6k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill tail-multi-pod-kubernetes-logs-by-label-during-incidents-with-stern
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Stern CLI, Kubernetes cluster access
Install & setup
Install Stern from the project repository or package manager, then run it against a namespace, label selector, or pod name pattern to stream matching logs during investigation.
Author
Stern maintainers
Publisher
Organization
Last updated
Apr 15, 2026
Quick brief
Use Stern when an agent needs to follow logs across many Kubernetes pods at once during an outage, rollout, or noisy incident. The agent can select pods by label or pattern, stream their logs together, and highlight which workload is failing or flapping. Invoke this instead of using the product normally when the task is multi-pod incident log triage, not general log platform setup or cluster administration. The boundary is targeted live log aggregation from Kubernetes workloads during diagnosis, not a generic logging product listing.