pickfit

BrowseInfra & DevOps tools

stern

Command-line tool that tails logs from multiple Kubernetes pods and containers at once, with color-coded output and regex filtering.

Tested on Linux

Use it

Linux x86_64

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. Download stern v1.35.0 linux_amd64 release tarball, extract, install into ~/.local/bin

    cd /tmp && TAG=$(curl -fsSLI -o /dev/null -w '%{url_effective}' https://github.com/stern/stern/releases/latest | sed 's#.*/tag/##') && V=${TAG#v} && curl -fsSLO https://github.com/stern/stern/releases/download/$TAG/stern_${V}_linux_amd64.tar.gz && tar xzf stern_${V}_linux_amd64.tar.gz && mkdir -p ~/.local/bin && install -m755 stern ~/.local/bin/stern
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

cd /tmp && TAG=$(curl -fsSLI -o /dev/null -w '%{url_effective}' https://github.com/stern/stern/releases/latest | sed 's#.*/tag/##') && V=${TAG#v} && curl -fsSLO https://github.com/stern/stern/releases/download/$TAG/stern_${V}_linux_amd64.tar.gz && tar xzf stern_${V}_linux_amd64.tar.gz && mkdir -p ~/.local/bin && install -m755 stern ~/.local/bin/stern
stern --version
cat > /home/sbx/work/service.log <<'EOF'
{"level":"info","msg":"server started","port":8080}
{"level":"error","msg":"db connection failed"}
plain text line: request handled
EOF
stern --stdin < service.log

Check that it works

stern --version

The output should contain “version: 1.35.0”.

First thing to try

cat > "$HOME"/work/service.log <<'EOF'
{"level":"info","msg":"server started","port":8080}
{"level":"error","msg":"db connection failed"}
plain text line: request handled
EOF
stern --stdin < service.log

Run stern --stdin < <file> to read log lines from a file, or point it at your Kubernetes cluster to tail pod logs.

What it does

  • See log output in color
    How to use it
    1. Add --color=always and a color function in the template, for example stern --stdin --color=always --template='{{ colorRed .Message }}{{"\n"}}' < <file>.
    Tested
  • Format log lines with your own Go templates
    How to use it
    1. Pass a Go template with --template, for example `stern --stdin --template='{{ with $msg := .Message | tryParseJSON }}[{{ $msg.level }}] {{ $msg.msg }}{{ else }}RAW: {{ .Message }}{{ end }}{{"\n"}}'
    2. Use tryParseJSON to read fields from JSON log lines and fall back to the raw message for plain lines.
    Tested
  • Tail logs from many pods and containers at once
    Not tested
  • Pick pods by regex or resource name
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 2 of 4 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • tail logs from all pods across all namespaces
  • tail pods created by a deployment
  • pipe Kubernetes logs as JSON to jq
  • show logs only for pods that are not ready

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version 1.35.0

Differences the test machine hit

  • README: go install github.com/stern/stern@latest / asdf / krew
    In the test: The box has no Go, asdf or krew, so I used the README's 'Download a binary release' option: stern_1.35.0_linux_amd64.tar.gz from GitHub releases, extracted into ~/.local/bin
  • README: stern --stdin < service.log
    In the test: The README provides no service.log; I wrote a small sample log file myself

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.