K9s CLI
The Kubernetes terminal interface shows resources and logs so users can inspect cluster state alongside agent work.
- 34,930 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Normal mode exposes resource changes and deletion, container shells and other cluster operations under the account’s permissions.
Install
Manual install
brew install derailed/k9s/k9sFirst command option via Homebrew for macOS or Linux; source indentation is preserved.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Normal mode exposes resource changes and deletion, container shells and other cluster operations under the account’s permissions.
This is third-party code. Review the repository files before installing.
What it does
K9s displays Kubernetes resources in interactive tables. Users switch contexts and namespaces, filter objects and inspect logs or resource details. An agent can prepare a list of suspicious pods for a person to investigate in the interface. The same UI supports edits, restarts, deletion, container shells and port forwarding. Read-only mode supports observation, while configuration and the chosen context’s permissions determine available actions.
Who it is for. On-call Kubernetes engineers checking an agent’s findings against live resources and logs.
Good fit when
- An agent identified problematic pods whose logs need inspection.
- During an incident, a user needs to compare resources across namespaces.
- A resource’s YAML and description should be inspected before an edit.
- Cluster observation needs an interface with modification commands disabled.
Not a fit when
- You need a fully noninteractive command for a CI script.
- The user lacks access to the selected cluster.
- The interactive client must itself understand natural-language requests.
Example request
Prepare a list of failing pods and a command to open the relevant K9s context read-only.Limitations
The interface expects a 256-color terminal, and an unsuitable environment can affect display. Resource editing needs an external editor configured through `EDITOR` or `KUBE_EDITOR`. The `--readonly` mode disables cluster modification commands, while normal mode exposes operations allowed by the account. Immediate deletion through `Ctrl+K` has no confirmation dialog, so use read-only mode for observation and verify the active context.
How to disable. Exit with `:quit` or `Ctrl+C`. Review resources already changed and objects created by external commands separately.
FAQ
How do I start without cluster changes?
Run `k9s --readonly`.
Where can I see keyboard help?
Press `?` in the current view.
How do I open a selected pod’s logs?
Press `l`; supported views use `p` for previous logs.
How do I view resource YAML?
Select the resource and press `y`.
What happens on deletion?
Regular deletion asks for confirmation, but immediate `Ctrl+K` does not.
Discussion
No questions or reviews yet.
Related
CLI toolsThe Kubernetes configuration manager merges connections and switches contexts so agents use the intended cluster.
The official Amazon EKS CLI creates and manages Kubernetes clusters from configuration that an agent can prepare for review.
A terminal shell for working with coding agents: embedded terminals, diffs, files, td tasks and worktrees side by side
A coding-agent monitor with a project component map and an experimental 3D kitchen view of ongoing tasks
One desktop window for Claude Code, Codex, Gemini CLI and OpenCode: terminals, pull requests, diffs and approvals
A terminal diff viewer: all files in one stream, and an agent with the hunk-review skill walks through the changes and leaves line comments
README in short
Name and label filters, resource relationships and command plugins are available. K9s uses existing Kubernetes contexts.