k9s

k9s, the Kubernetes terminal UI, with kubectl, on FreeBSD. Mount your kubeconfig and run it interactively.

Version Tags

Before deploying, ensure your host environment is ready. See the Quick Start Guide for host setup instructions, including the security model for host vs. container privileges.

Deployment

1
2
3
4

podman run --rm \
  -v /containers/k9s/kubeconfig:/kubeconfig:ro \
  -v /containers/k9s:/config # optional \
  ghcr.io/daemonless/k9s:pkg

Save as run.sh, then run sh run.sh.

Setup Instructions

It is a terminal UI: run it interactively, with your kubeconfig mounted read-only:

1

podman run --rm -it -v ~/.kube/config:/kubeconfig:ro ghcr.io/daemonless/k9s:latest

kubectl is in the image too: podman run --rm -it -v ~/.kube/config:/kubeconfig:ro --entrypoint kubectl ghcr.io/daemonless/k9s:latest get pods -A.

The image runs as uid 1000. A kubeconfig that only its owner can read (the usual 0600) must belong to uid 1000, or be readable by it; otherwise k9s stops with permission denied on /kubeconfig. Copy it somewhere readable, or add --user 0.

A kubeconfig that points at localhost (a cluster on this same machine) needs --network host, so that address means the host and not the container.

Settings, skins, plugins and k9s's own logs go to /config; mount it to keep them between runs.

Interactive Configuration

Parameters

Volumes

Need help? Join our Discord community.