If you manage Kubernetes every day, you know the routine: kubectl get pods, copy a pod name, kubectl describe, kubectl logs, switch namespace, and start over. It works, but it is slow, and it only ever shows you one small slice of a cluster that is constantly changing. k9s fixes that. It is an open-source terminal UI that turns your cluster into a live, navigable dashboard without ever leaving the terminal.
A good management console is half the job; k9s is the tool that made Kubernetes administration feel just as manageable to me.
What is k9s?
k9s is a terminal-based user interface for Kubernetes. It reads the same kubeconfig file as kubectl and talks to the same Kubernetes API, using your existing RBAC permissions. That means there is nothing to deploy inside the cluster, no agents, and no extra ports to open. It works the same way against Amazon EKS, Google GKE, Azure AKS, k3s, or a homelab cluster.
Installing it takes seconds:
# macOS / Linux brew install k9s # Windows winget install k9s # Start k9s in a specific context and namespace k9s --context prod-cluster -n web
Why administrators should use k9s
A live overview of the whole cluster
kubectl gives you a snapshot. k9s gives you a live view. Pods, deployments, nodes, and services refresh continuously, and status is color-coded, so a pod stuck in CrashLoopBackOff or Pending stands out immediately. Instead of piecing the picture together from a dozen commands, you see the state of your workloads on one screen.
Faster troubleshooting
The classic debug loop of finding a pod, describing it, reading its logs, and opening a shell becomes a few keystrokes. Highlight a pod and press l for logs, d to describe, s for a shell, or Shift+F to port-forward. No more copying long, generated pod names between commands. During an incident, that saved time matters.
Drill down through relationships
k9s lets you move from a deployment to its pods, and from a pod to its containers, by pressing Enter. The :xray view shows how resources relate to each other as a tree, which makes it far easier to understand what a Helm chart or operator has actually created.
Safe context and namespace switching
Working with several clusters is where mistakes happen. k9s always shows the active context and namespace in the header, and switching is as simple as typing :ctx or :ns. For read-only investigations, start it with k9s --readonly to disable every action that modifies the cluster. This is ideal for giving support staff or junior administrators visibility without risk.
Resource usage at a glance
When the metrics-server is installed, k9s shows CPU and memory usage for pods and nodes, including usage as a percentage of requests and limits. The :pulses view gives a quick health summary of the whole cluster. It is not a replacement for Prometheus and Grafana, but it answers the question “what is happening right now?” in seconds.
Keyboard-driven and customizable
Everything in k9s is driven by the keyboard, and the commands mirror the resource names you already know from kubectl. You can add your own aliases, hotkeys, skins, and plugins, so the tool adapts to the way your team works.
Essential k9s shortcuts
:pod, :deploy, :svc, :node:ctx / :ns0/Enterd / ylseShift+FCtrl+D / Ctrl+K?Esc / :qkubectl cheat sheet
k9s does not replace kubectl. You still need it for scripts, CI/CD pipelines and quick one-liners. Here are the commands I use most.
kubectl config current-contextkubectl config get-contextskubectl config use-context <name>kubectl config set-context --current --namespace=<ns>kubectl get pods -Akubectl get pods -o widekubectl describe pod <pod>kubectl logs -f <pod> -c <container>kubectl logs <pod> --previouskubectl exec -it <pod> -- /bin/shkubectl apply -f deployment.yamlkubectl scale deploy <name> --replicas=3kubectl rollout restart deploy <name>kubectl rollout status deploy <name>kubectl rollout undo deploy <name>kubectl port-forward svc/<svc> 8080:80kubectl top pods / kubectl top nodeskubectl get events --sort-by=.lastTimestampkubectl drain <node> --ignore-daemonsetskubectl get deploy <name> -o yamlk9s and kubectl: better together
Use kubectl for automation and repeatable changes, and k9s for everything you do interactively: exploring, monitoring, and troubleshooting. Together they give administrators both precision and a clear overview of what is running in their clusters. If you work with Kubernetes on AWS, Google Cloud, or in your homelab, install k9s today. It is one of the easiest productivity wins in the Kubernetes ecosystem.